provider migrate cloudant #46405
Merged
provider migrate cloudant #46405
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The provider schema previously supported this field but it was dropped during the provider migration project. Cloudant is the only provider at the time of writing which makes use of this mechanism
o-nikolas
requested review from
ashb,
jedcunningham and
potiuk
as code owners
boring-cyborg
bot
added
area:dev-tools
area:providers
kind:documentation
provider:cloudant
labels
o-nikolas
commented
Feb 4, 2025
o-nikolas
commented
Feb 4, 2025
dev/breeze/src/airflow_breeze/prepare_providers/provider_documentation.py
Outdated
Show resolved
Hide resolved
o-nikolas
commented
Feb 4, 2025
potiuk
reviewed
Feb 4, 2025
dev/breeze/src/airflow_breeze/prepare_providers/provider_documentation.py
Outdated
Show resolved
Hide resolved
potiuk
reviewed
Feb 4, 2025
dev/breeze/src/airflow_breeze/prepare_providers/provider_documentation.py
Outdated
Show resolved
Hide resolved
potiuk
approved these changes
Feb 4, 2025
potiuk
reviewed
Feb 4, 2025
potiuk
reviewed
Feb 4, 2025
potiuk
reviewed
Feb 4, 2025
potiuk
reviewed
Feb 4, 2025
dev/breeze/src/airflow_breeze/prepare_providers/provider_documentation.py
Outdated
Show resolved
Hide resolved
If it is not already present add a wild card for all patch releases of an excluded python version
With functional version exclusion in requires-python working, many things in our CI are not setup to support this. So go back to "soft" or non-functional exclusions. This will at least update the classifiers
Contributor
Author
|
@potiuk |
Member
|
Indeed. Looks good. The fix to main is coming #46492 |
potiuk
approved these changes
Feb 5, 2025
insomnes
pushed a commit
to insomnes/airflow
that referenced
this pull request
Feb 6, 2025
* Update provider schema to include excluded-python-versions The provider schema previously supported this field but it was dropped during the provider migration project. Cloudant is the only provider at the time of writing which makes use of this mechanism * Migrate Cloudant provider to new structure * Updates from PR feedback * Add wildcard for all patch releases of an excluded python version If it is not already present add a wild card for all patch releases of an excluded python version * Fix install_airflow script to remove cloudant on 3.9 * Remove more spaces * Remove the fix for version exclusions With functional version exclusion in requires-python working, many things in our CI are not setup to support this. So go back to "soft" or non-functional exclusions. This will at least update the classifiers
niklasr22
pushed a commit
to niklasr22/airflow
that referenced
this pull request
Feb 8, 2025
* Update provider schema to include excluded-python-versions The provider schema previously supported this field but it was dropped during the provider migration project. Cloudant is the only provider at the time of writing which makes use of this mechanism * Migrate Cloudant provider to new structure * Updates from PR feedback * Add wildcard for all patch releases of an excluded python version If it is not already present add a wild card for all patch releases of an excluded python version * Fix install_airflow script to remove cloudant on 3.9 * Remove more spaces * Remove the fix for version exclusions With functional version exclusion in requires-python working, many things in our CI are not setup to support this. So go back to "soft" or non-functional exclusions. This will at least update the classifiers
ambika-garg
pushed a commit
to ambika-garg/airflow
that referenced
this pull request
Feb 17, 2025
* Update provider schema to include excluded-python-versions The provider schema previously supported this field but it was dropped during the provider migration project. Cloudant is the only provider at the time of writing which makes use of this mechanism * Migrate Cloudant provider to new structure * Updates from PR feedback * Add wildcard for all patch releases of an excluded python version If it is not already present add a wild card for all patch releases of an excluded python version * Fix install_airflow script to remove cloudant on 3.9 * Remove more spaces * Remove the fix for version exclusions With functional version exclusion in requires-python working, many things in our CI are not setup to support this. So go back to "soft" or non-functional exclusions. This will at least update the classifiers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrates the Cloudant provider.
static and unit tests pass.
This provider required changes to the new provider schema to add back support for excluded python versions which cloudant makes use of (see comment annotations for more details). The release management scripts for generating project toml files also needed updating.
related: #46045
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.