Skip to content
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 June 20, 2023 #32030

Closed
50 of 86 tasks
eladkal opened this issue Jun 20, 2023 · 22 comments
Closed
50 of 86 tasks

Status of testing Providers that were prepared on June 20, 2023 #32030

eladkal opened this issue Jun 20, 2023 · 22 comments
Labels
kind:meta High-level information important to the community testing status Status of testing releases

Comments

@eladkal
Copy link
Contributor

eladkal commented Jun 20, 2023

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: 8.2.0rc1

Provider apache.hive: 6.1.1rc1

Provider apache.livy: 3.5.1rc1

Provider apache.spark: 4.1.1rc1

Provider atlassian.jira: 2.1.1rc1

Provider cncf.kubernetes: 7.1.0rc1

Provider databricks: 4.3.0rc1

Provider discord: 3.3.0rc1

Provider google: 10.2.0rc1

Provider hashicorp: 3.4.1rc1

Provider jdbc: 4.0.0rc1

Provider microsoft.azure: 6.1.2rc1

Provider microsoft.mssql: 3.4.1rc1

Provider mysql: 5.1.1rc1

Provider odbc: 4.0.0rc1

Provider pagerduty: 3.3.0rc1

Provider smtp: 1.2.0rc1

Provider snowflake: 4.2.0rc1

The guidelines on how to test providers can be found in

Verify providers by contributors

All users involved in the PRs:
@o-nikolas @utkarsharma2 @phanikumv @nathadfield @simonprydden @vargacypher @svdimchenko @longslvr @dstandish @uranusjr @dimonchik-suvorov @vincbeck @melugoyal @eladkal @Joffreybvn @sunank200
@moiseenkov @pankajastro @potiuk @killua1zoldyck @hussein-awala @raphaelauv @enchant3dmango @Lee-W @Adaverse @vandonr-amz @syedahsn @ying-w @bkossakowska @VladaZakharova @mahammi @pankajkoti @pgagnon

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.
@eladkal eladkal added kind:meta High-level information important to the community testing status Status of testing releases labels Jun 20, 2023
@raphaelauv
Copy link
Contributor

apache/airflow:slim-2.6.2-python3.11 with
apache-airflow-providers-cncf-kubernetes==7.1.0rc1

on a kubernetes-sigs/kind

KubernetesResourceOperator - KubernetesDeleteResourceOperator & KubernetesCreateResourceOperator (#29930):

👌

@pankajkoti
Copy link
Member

pankajkoti commented Jun 20, 2023

Verified that my changes in #31201 and #31849 are included in the RCs and that they look good. Tested both with corresponding example DAGs and they yield expected results ✅

Thank you for including this! 🙂

@enchant3dmango
Copy link
Contributor

apache-airflow-providers-apache-spark==4.1.1rc1. ✅

Thank you! 🖖🏼

@simonprydden
Copy link
Contributor

Verified my change in #31574 is included in the RC and working.

Thank you.

@Adaverse
Copy link
Contributor

Tested #31765 works as expected.

Can we include #31783 in this release @eladkal @phanikumv?

@Joffreybvn
Copy link
Contributor

JiraOperator (#31672) works like a charm, thanks !

@vandonr-amz
Copy link
Contributor

good for me 👍

@vargacypher
Copy link
Contributor

Tested apache-airflow-providers-discord==3.3.0rc1 ✅
image

@killua1zoldyck
Copy link
Contributor

#31837 Works as expected

@longslvr
Copy link
Contributor

#31171 is good to go!

@vincbeck
Copy link
Contributor

#31622 works as expected. My other changes are style related

github-actions bot pushed a commit to astronomer/astronomer-providers that referenced this issue Jun 21, 2023
@Lee-W
Copy link
Member

Lee-W commented Jun 21, 2023

#31482 works as expected and we have successfully tested other providers using our sample DAGs without any issues.

pankajkoti pushed a commit to astronomer/astronomer-providers that referenced this issue Jun 21, 2023
@eladkal
Copy link
Contributor Author

eladkal commented Jun 21, 2023

Can we include #31783 in this release @eladkal @phanikumv?

This PR is not merged yet. Once it's merged it will be released in a the following wave

@phanikumv
Copy link
Contributor

Tested #30279, #31685, #31081,#31317 , #31249, #31758 as part of below RC and they are working as expected.

apache-airflow-providers-amazon==8.2.0rc1
pip install apache-airflow-providers-apache-livy==3.5.1rc1
pip install apache-airflow-providers-google==10.2.0rc1

github-actions bot pushed a commit to astronomer/astronomer-providers that referenced this issue Jun 22, 2023
@ying-w
Copy link
Contributor

ying-w commented Jun 22, 2023

please remove #31338 it is not working as expected, I just pushed up a fix for it

@eladkal
Copy link
Contributor Author

eladkal commented Jun 22, 2023

please remove #31338 it is not working as expected, I just pushed up a fix for it

We can not remove. The choices are cancel RC1 and cut RC2 or release anyway.
Assuming this is the only issue I prefer to release anyway since this is a new small enhancement which won't cause any user pain if it's not working as expected.
I will cut a followup release for the google provider with the fix as soon as this wave is released.

@utkarsharma2
Copy link
Contributor

utkarsharma2 commented Jun 22, 2023 via email

@pankajastro
Copy link
Member

#30244, #30865 and #30945 looks good. #31703 We reverted in #31985. So all good. thank you!

@hussein-awala
Copy link
Member

I tested:

I cannot test #31991 because I don't have a GCP setup, but it's present in the release and it should work according to the GCP documentation

@potiuk
Copy link
Member

potiuk commented Jun 22, 2023

Checked if #27264 , #31983 , #31780, #31984 are included. All looks good.

github-actions bot pushed a commit to astronomer/astronomer-providers that referenced this issue Jun 23, 2023
@melugoyal
Copy link
Contributor

validated #31659, looks good

@eladkal
Copy link
Contributor Author

eladkal commented Jun 23, 2023

Thank you everyone.
Providers are released
I invite everyone to help improve providers for the next release, a list of open issues can be found here.

@eladkal eladkal closed this as completed Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:meta High-level information important to the community testing status Status of testing releases
Projects
None yet
Development

No branches or pull requests