Add unit test for PostgresHook with invalid connection id

[KL-2300032590]

This pull request adds a unit test to ensure that PostgresHook fails fast
when initialized with an invalid postgres_conn_id.

The test improves defensive coverage for the Postgres provider by validating
error handling for incorrect hook configuration.

Note: Tests could not be executed locally due to missing Airflow pytest plugins.
Relying on CI for validation.

---

Was generative AI tooling used to co-author this PR?

• Yes (ChatGPT)

Generated-by: ChatGPT following the Apache Airflow guidelines

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[Prab-27]

You could also pass Airflow specific exceptions .

I believe something wrong here with - indentation ?

[KL-2300032590]

Yes,i will fix it and point on the exception type — I’ll update the test to assert an Airflow-specific exception (AirflowException) instead of the generic Exception..&
I’ll push the exception fix shortly and update the PR.

Appreciate the guidance!

[Prab-27]

@KL-2300032590 Thanks !!

The defaults properties are defined here-

airflow/providers/postgres/src/airflow/providers/postgres/hooks/postgres.py

Line 138 in 0ede1b2

default_conn_name = "postgres_default"

You can easily run these tests locally - unit -tests- docs

You could also run static checks locally - using prek hook docs

[KL-2300032590]

I’ve updated the test to use an Airflow-specific exception (AirflowConfigException) and verified the indentation.

Please let me know if this looks good now.

[dabla]

I’ve updated the test to use an Airflow-specific exception (AirflowConfigException) and verified the indentation.

Please let me know if this looks good now.

This test looks a bit weird to me, I would expect this be a general behaviour, not only for PostgresHook?

[potiuk]

Sounds like not really consequential AI generated test.

[Prab-27]

I tested this -
Yes it shows default value since don't need to add this test