-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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 April 07, 2022 #22836
Comments
From my side the testing for Google was done :) #22311 |
All mine are doc and sample dag related so it's all good |
From my side, test run of BigQueryToGCSOperator was done. #22506 |
I can't check the KPO because it ask for
|
Actually .. you can :) (see below).
That's cool and how it should be (except that it asks for But to be cool - you actually can test it. You can install the provider in regular "main" breeze. The breeze in Just remove sources of airflow/providers/cncf in |
thanks @potiuk, I was not aware of since Airflow ( without the kubernetesExectutor ) do not have Kubernetes as a dependency it's possible to install apache-airlfow==2.2.5
kubernetes==21.7.0
apache-airflow-providers-cncf-kubernetes==4.0.0rc1 --no-deps Is there any feature of airflow 2.3 that restrict the usage of the kubernetes provider 4.0.X in airlfow 2.2.5 ? otherwise #22412 -> WORK |
otherwise #22412 -> WORK
Yeah. The main problem is that Airlfow 2.2.5 has KubernetesExecutor that both - uses cncf.kubernetes provider to run AND relies on old < 20.0.0 of The new provider depend on > 21 (for good reasons) and rather than risk that there are more things not working in Airflow 2.2.5 - we decided that 2.2.* line and before will have to stick with the old (well - not THAT old) kubernetes provider. Hopefully there will not be serious "issues" with the old provider (we can always release a critical fix for the the 3.* line of provider). But if you would like to use new features from kubernetes provider 4.0+, you will have to go Airflow 2.3+. As a bonus, that might actually give people more incentive to move to Airlfow 2.3 at some point in time :). |
BTW. As a learning - in the future we might bundle K8s Executor with the provider, but that will require Airflow 3 and breaking changes I am afraid. |
tested discord provider (#22570) and it works |
My changes are docs/example dags, so all good. |
#22710 (google 6.8.0rc1) works as expected on 2022/04/09 |
#22772: Tested (google 6.8.0rc1) working as expected |
Thanks. Re #22422 - it depends on the bug - if it's a bug in new operators which can be wokrarounded or does not block things entirely, we can still release the rc1 and follow up in the next release of the provider. We'd only refrain from releasing a provider for sure if there is a serious regression. |
Ah.. Then yeah :) rc2 it is. Good that you tested ! |
#22519 is good! Just a few docstring changes but confirmed in the package files. |
Double checked #22667 validated custom headers are delivered in the resulting email delivery |
Thanks for testing everyone! I proceed with the release of all providers except the Databricks one. RC2 for databricks follows. |
Body
I have a kind request for all the contributors to the latest provider packages release.
Could you please help us to test the RC versions of the providers?
Let us know in the comment, whether the issue is addressed.
Those are providers that require testing as there were some substantial changes introduced:
Provider amazon: 3.3.0rc1
Provider apache.livy: 2.2.3rc1
Provider celery: 2.1.4rc1
Provider cncf.kubernetes: 4.0.0rc1
Provider databricks: 2.6.0rc1
DatabricksJobRunLink
to not create ad hoc TaskInstances (#22571): @josh-fellProvider discord: 2.1.4rc1
Provider docker: 2.6.0rc1
DockerOperator
(#22502): @BowrnaProvider elasticsearch: 3.0.3rc1
Provider google: 6.8.0rc1
download_media
url inGoogleDisplayVideo360SDFtoGCSOperator
(#22479): @pierrejeambrunCloudBuildRunBuildTriggerOperator
fail to find build id. (#22419): @stephenokenProvider hashicorp: 2.2.0rc1
Provider jenkins: 2.1.0rc1
JenkinsBuildSensor
(#22421): @SasanAhmadiProvider microsoft.azure: 3.8.0rc1
AzureCosmosDocumentSensor
(#22735): @kaxilProvider microsoft.psrp: 1.1.4rc1
Provider presto: 2.2.0rc1
Provider sftp: 2.6.0rc1
Provider trino: 2.2.0rc1
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: