Allow providers to add default connections
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 484
Description
### Body
Currently we can add default connections only by adding entry to:
https://github.com/apache/airflow/blob/00e10560983b4cff7279100b9cf5cd5dd8cdf877/airflow/utils/db.py#L116
This means only Airflow core release can add the new default connection which is not in sync with providers.
Examples:
https://github.com/apache/airflow/pull/31533#discussion_r1236704083
https://github.com/apache/airflow/pull/31787#discussion_r1234913952
This is a pain because providers support earlier Airflow version (for example right now the minimum Airlfow version supported by providers is Airflow 2.4.0 so even if we add new connection to core and release it with Airflow 2.7.0 the users of 2.4.0 won't have it)
**The task:**
We need somehow to make it so that providers can add default connections (and extract the existed default provider connections from core)
### Committer
- [X] I acknowledge that I am a maintainer/committer of the Apache Airflow project.
Contributor guide
Research direction
Start with the default-connection entry in airflow/utils/db.py and review the linked pull-request discussions for the provider compatibility constraints. Define how providers can supply default connections and how existing provider connections should move out of core; done means provider releases can provide them across supported Airflow versions without relying on a new core release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100