-
Notifications
You must be signed in to change notification settings - Fork 13.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status of testing Providers that were prepared on March 15, 2022 #22264
Comments
Hello everyone. this is the out-of-bands release of all providers - with Trove Classifiers from PyPI added (Once we release them - they will all appear in https://pypi.org/search/?q=&o=&c=Framework+%3A%3A+Apache+Airflow&c=Framework+%3A%3A+Apache+Airflow+%3A%3A+Provider) In Amazon, I marked all the changes that were tested in the previous candidate). |
#21422 -> OK: Improve docs with more example tasks |
We are getting fast a serious coverage this time :) . |
#22157 OK |
#19137 OK |
#21785 -> OK: Enable remote logging into Alibaba Cloud OSS |
Thanks @repl-mike-roest for out-of-list tests! Great open-source-spirit! |
Yeah. New providers aren't here :) |
Thanks for all the testing. We will have to release a new wave, as there was a general issue found in #22380 (but there will be just a few new changes to vote). |
dumb question: will these new providers show up in the constraints-2.2.4/constraints-3.8.txt? or be pushed to Airflow 2.2.5? |
The latter. The constraints for each version contain the "snapshot" of providers that are available during release. Constraints for released version (so You are free to upgrade the new providers individually as described in https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html#installation-and-upgrading-of-airflow-providers-separately (just mind that this wave will be re-run as they have mistakenly two extra packages as dependencies so I think about yanking all of them after we release a new wave). But for the "base" installation of airflow using constraints, stability of the installation is more important than using newer providers. |
gotcha! thanks! i must have missed my orientation or suffered from foggy brain on Mondays. what does "yanking them" mean? 😅 |
aha! to save face, i'll say "no wonder it sounds so familiar" |
Body
Provider alibaba: 1.1.0rc1
Provider amazon: 3.1.1rc1
RedshiftSQLOperator
(#21885): @kaxilProvider databricks: 2.4.0rc1
Provider docker: 2.5.1rc1
Provider google: 6.6.0rc1
chunk_size
inGoogleDriveHook
standard (#22222): @ulscProvider snowflake: 2.5.2rc1
The guidelines on how to test providers can be found in
Verify providers by contributors
Committer
The text was updated successfully, but these errors were encountered: