Add IBM Db2 provider with Hook

[Amitkumar293]

Description

This PR adds a new provider for IBM Db2 database support in Apache Airflow.

What: New Db2 provider package with Hook and Operator
Why: Enable Airflow users to connect to and execute queries against IBM Db2 databases

Changes

• Db2Hook: Extends DbApiHook for IBM Db2 connectivity with SSL support
• Added Db2Dialect: - Mentioned the SQLAlchemy dialect component
• Comprehensive unit tests (Tests covering all functionality)
• Documentation and example DAGs
• Provider metadata and configuration

Testing

• ✅ All unit tests passing
• ✅ Ruff linting and formatting checks passed
• ✅ Follows Airflow coding standards

---

Important

🛠️ Maintainer triage note for @Amitkumar293 · by @potiuk · 2026-07-28 16:22 UTC

Helpful heads-up from the maintainers — please address before this PR can be reviewed:

• ❌ Pre-commit / static checks. See docs.

The ball is in your court — you've been assigned to this PR. Fix the above, then mark it Ready for review.

See the Pull Request quality criteria for how to fix each item. There is no rush.

_{Automated triage — may be imperfect; a maintainer takes the next look. We use this two-stage triage process so maintainers' limited time goes to the conversation with you.}

[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
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

[jscheffl]

Note, that some fomality with announcement/DISCUSS is neede to add a new provider, following https://github.com/apache/airflow/blob/main/providers/ACCEPTING_PROVIDERS.rst

[Amitkumar293]

Note, that some fomality with announcement/DISCUSS is neede to add a new provider, following https://github.com/apache/airflow/blob/main/providers/ACCEPTING_PROVIDERS.rst

Thanks for pointing this out.

I’ve created a DISCUSS thread on the dev@airflow.apache.org mailing list for the new IBM Db2 provider, following the ACCEPTING_PROVIDERS.rst process.

[github-actions]

uv.lock on main just moved via commit fd0f7e2 and this PR currently conflicts.

Quickest fix:

git fetch upstream main && git rebase upstream/main
rm uv.lock && uv lock
git add uv.lock && git rebase --continue
git push --force-with-lease

Automated nudge — ignore if you're not ready to rebase. This comment is updated in place on future uv.lock bumps.

[Amitkumar293]

@jscheffl Thanks for your review, very helpful. I am working on the review comments.

[eladkal]

Was there a mailing list thread about this new provider?
https://github.com/apache/airflow/blob/main/providers/ACCEPTING_PROVIDERS.rst#examples-of-current-process