Constrain versions for Providers during docker build for 2.0.0 #212
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.
Since we are planning to cut 2.0.0-3 we should release the same set of Providers except for few exceptions:
apache-airflow-providers-elasticsearch==1.0.1
-- contains our logging fixapache-airflow-providers-cncf-kubernetes==1.0.1
-- contains a bug fix for K8s Operatorapache-airflow-providers-microsoft-azure==1.1.0
-- Will allow installing snowflake provider (includes apache/airflow#12188)Since these constraint sare only used in docker build time and not included in Dockerfile users are free to upgrade to a major version for providers like google. This is the main different between this constraints file vs
pip-constraints.txt
.Without this change, new versions of providers would be installed (even the major ones)