-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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 August 26, 2023 #33751
Comments
I also tested #33601 and it no longer has the ImportError warning, as expected |
I have just tested #33314, works as expected. |
I haved tested #33652, looks good. |
I have tested #33005 this morning. Messages indicate Service Principal Token is being used, and data was retrieved from a Databricks Workspace. |
Checked all my changes. All look good! |
Tested #33457 and it works fine |
Checked #33483 and it is present in the different providers. |
Tested my changes:
Things do not seem to have regressed and it works as expected. Ran a few dags to target the cncf provider too. It looks good to me. Thanks! |
Tested my changes, everything looks good. |
#32883 looks good |
#32910 works as expected. |
tested #33656 and it looks good |
tested #33219 and it looks good. |
tested #33500, works as expected |
good for me |
Thank you everyone. I invite everyone to help improve providers for the next release, a list of open issues can be found here. |
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?
The guidelines on how to test providers can be found in
Verify providers by contributors
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: 8.6.0rc1
deferrable
option toLambdaCreateFunctionOperator
(#33327): @vincbecksql_hook_params
parameter toS3ToSqlOperator
(#33427): @alexbeggsql_hook_params
parameter toSqlToS3Operator
(#33425): @alexbeggGlueJobOperator
(#33408): @erdos2nstart_time
(#33673): @vincbeckSageMakerEndpointOperator
(#33487): @vandonr-amzEcsRunTaskOperator
(#33703): @vandonr-amzboto3.client
linked to resource meta instead of create new one for waiters (#33552): @TaragolisProvider apache.beam: 5.2.2rc1
Provider apache.hive: 6.1.5rc1
Provider apache.pinot: 4.1.3rc1
Provider celery: 3.3.3rc1
Provider cncf.kubernetes: 7.5.0rc1
active_deadline_seconds
parameter toKubernetesPodOperator
(#33379): @amoghrajeshProvider databricks: 4.4.0rc1
Provider elasticsearch: 5.0.1rc1
Provider exasol: 4.2.4rc1
Provider influxdb: 2.2.2rc1
Provider microsoft.azure: 6.3.0rc1
Provider mysql: 5.3.0rc1
init_command
parameter toMySqlHook
(#33359): @alexbegglocal_infile
parameter toS3ToMySqlOperator
(#33459): @benchoncyProvider openlineage: 1.0.2rc1
Provider oracle: 3.7.3rc1
Provider salesforce: 5.4.2rc1
Provider sftp: 4.6.0rc1
Provider slack: 8.0.0rc1
Provider snowflake: 5.0.0rc1
S3ToSnowflake
andSnowflakeToSlack
operators (#33558): @Taragolisapache-airflow-providers-snowflake
due to breaking changes (#33615): @TaragolisProvider trino: 5.3.0rc1
Provider yandex: 3.4.0rc1
All users involved in the PRs:
@amoghrajesh @mobuchowski @zbstof @johnbrandborg @vincbeck @JDarDagran @benchoncy @ellisms @SamWheating @pankajastro @alexbegg @sunank200 @zinal @LipuFei @functicons @hussein-awala @ephraimbuddy @Lee-W
@arjunanan6 @erdos2n @vandonr-amz @fdemiane @Owen-CH-Leung @phanikumv @Taragolis @mati-o @syedahsn @tiranux @covidium @yermalov-here @potiuk
Committer
The text was updated successfully, but these errors were encountered: