-
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 June 20, 2023 #32030
Comments
on a KubernetesResourceOperator - KubernetesDeleteResourceOperator & KubernetesCreateResourceOperator (#29930): 👌 |
Thank you! 🖖🏼 |
Verified my change in #31574 is included in the RC and working. Thank you. |
Tested #31765 works as expected. Can we include #31783 in this release @eladkal @phanikumv? |
JiraOperator (#31672) works like a charm, thanks ! |
good for me 👍 |
#31837 Works as expected |
#31171 is good to go! |
#31622 works as expected. My other changes are style related |
#31482 works as expected and we have successfully tested other providers using our sample DAGs without any issues. |
This PR is not merged yet. Once it's merged it will be released in a the following wave |
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. |
Tested #31207, <#31207> #31359
<#31359> #30698
<#30698> and they are working as
expected.
Thanks,
Utkarsh Sharma
…On Thu, Jun 22, 2023 at 11:31 AM eladkal ***@***.***> wrote:
please remove #31338 <#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.
—
Reply to this email directly, view it on GitHub
<#32030 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADDLAHNDYBA6G5EMZJ56FO3XMPNT5ANCNFSM6AAAAAAZNI7N2Y>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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 |
validated #31659, looks good |
Thank you everyone. |
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
BatchSensor
(#30279): @phanikumvdeferrable
param inEmrContainerSensor
(#30945): @pankajastrowait_for_completion
fromEcsRegisterTaskDefinitionOperator
andEcsDeregisterTaskDefinitionOperator
(#31884): @vandonr-amzProvider apache.hive: 6.1.1rc1
Provider apache.livy: 3.5.1rc1
LivyOperator
(#31685): @phanikumvProvider apache.spark: 4.1.1rc1
Provider atlassian.jira: 2.1.1rc1
Provider cncf.kubernetes: 7.1.0rc1
Provider databricks: 4.3.0rc1
DatabricksSubmitRunOperator
: Fix type annotation forlibraries
param (#31888): @phanikumvProvider discord: 3.3.0rc1
DiscordNotifier
(#31273): @vargacypherProvider google: 10.2.0rc1
BaseSQLToGCSOperator
(#31831): @hussein-awalacacheControl
field to google cloud storage (#31338): @ying-wpreserveAsciiControlCharacters
tosrc_fmt_configs
for GCStoBQ (#31643): @nathadfieldGCSUploadSessionCompleteSensor
(#31081): @phanikumvDataprocSubmitJobOperator
(#31317): @phanikumvBigQueryInsertJobOperator
(#31249): @phanikumvBigQueryCheckOperator
(#31758): @phanikumvProvider hashicorp: 3.4.1rc1
userpass
andaws_iam
methods (#31593): @hussein-awalaProvider 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
The text was updated successfully, but these errors were encountered: