Closed eladkal closed 1 year ago
Contributors are also encouraged to cast non-binding vote in the mailing list thread.
Provider yandex: 3.3.0rc1 has been tested. all is fine 👌
all good for me as it's covered by a system test that's green
Snowflake change has unit test coverage 👍
Provider google: 8.11.0rc1 : I tested #29394 and it works as expected. Provider sftp: 4.2.4rc1: Same for #29794. Provider hashicorp: 3.3.0rc1: I have tested #29734 and it works, but currently we should use the same variables, config and connections paths for all the mount points because there is a bug in the Vault secrets backend, I wonder if we can add #29908 to this release or we add it to the next one.
@hussein-awala I will cancel RC1 for hashicorp provider and will cut RC2 after the current vote
Tested #29347 for SSH provider 3.5.0rc1 - works as expected. Waiting for full release!
aws_conn_id
which is not set to default one "aws-default". cc: @dominikhei this change fix problem that you described in #29504, if you would like, you also could test this Amazon Provider packageI checked apache-airflow-providers-amazon
and the change in #29708 is working as expected.
Provider telegram: 4.0.0rc1 works as expected 👍
for the kubernetes the name of the feature is incorrect
KubernetesPodOperator._render_nested_template_fields improved by changing the conditionals for a map (#29760): @jose-lpa
->
KubernetesPodOperator._render_nested_template_fields improved by changing the conditionals (#29760): @jose-lpa
( there is no map )
for the kubernetes the name of the feature is incorrect
KubernetesPodOperator._render_nested_template_fields improved by changing the conditionals for a map (#29760): @jose-lpa
->
KubernetesPodOperator._render_nested_template_fields improved by changing the conditionals (#29760): @jose-lpa
( there is no map )
The release mechanism currently does not allow us to change the commit messages. Probably something we need to improve on in the future. Since this is only issue with the commit title and not with the actual functionality I see no reason why we can't continue with release of this package.
Thanks for organizing @eladkal!
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.
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: 7.3.0rc1
wait_for_completion
param inRedshiftCreateClusterOperator
(#29657): @pankajastroRedshiftDataOperator
replaceawait_result
withwait_for_completion
(#29633): @eladkalProvider apache.flink: 1.0.1rc1
Provider apache.livy: 3.3.0rc1
Provider atlassian.jira: 2.0.1rc1
jira_method_args
in JiraOperator when not provided (#29741): @josh-fellProvider cncf.kubernetes: 5.2.2rc1
KubernetesPodOperator._render_nested_template_fields
improved by changing the conditionals for a map (#29760): @jose-lpaProvider common.sql: 1.3.4rc1
Provider dbt.cloud: 3.1.0rc1
DbtCloudJobRunAsyncSensor
(#29695): @phanikumvProvider github: 2.2.1rc1
github_method_args
in GithubOperator when not provided (#29699): @josh-fellProvider google: 8.11.0rc1
CloudSQLCloneInstanceOperator
(#29726): @FloMomcheck-for-inclusive-language
CI check (#29549): @josh-fellProvider hashicorp: 3.3.0rc1
Provider mysql: 4.0.2rc1
Provider sftp: 4.2.4rc1
Provider ssh: 3.5.0rc1
Provider telegram: 4.0.0rc1
Provider yandex: 3.3.0rc1
The guidelines on how to test providers can be found in Verify providers by contributors
All users involved in the PRs: @kristopherkane @sunank200 @LMnet @phanikumv @jose-lpa @pdebelak @ferruzzi @vincbeck @r-richmond @vandonr-amz @eladkal @wiktorn @maxnathaniel @pgagnon @hussein-awala @bkossakowska @Taragolis @pankajastro @fritz-astronomer @romibuzi @josh-fell @lwyszomi @potiuk @s0neq @Aakcht @FloMom @IKholopov @yehoshuadimarsky
Committer