Status of testing Providers that were prepared on March 03, 2023

@yehoshuadimarsky

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

Provider apache.flink: 1.0.1rc1

Make cncf.kubernetes required for flink provider (#29710): @potiuk

Provider apache.livy: 3.3.0rc1

Add Livy Operator with deferrable mode (#29047): @sunank200

Provider atlassian.jira: 2.0.1rc1

Handle jira_method_args in JiraOperator when not provided (#29741): @josh-fell

Provider cncf.kubernetes: 5.2.2rc1

KubernetesPodOperator._render_nested_template_fields improved by changing the conditionals for a map (#29760): @jose-lpa

Provider common.sql: 1.3.4rc1

fix do_xcom_push=False bug in SnowflakeOperator (#29599): @fritz-astronomer

Provider dbt.cloud: 3.1.0rc1

Add DbtCloudJobRunAsyncSensor (#29695): @phanikumv

Provider github: 2.2.1rc1

Handle github_method_args in GithubOperator when not provided (#29699): @josh-fell

Provider google: 8.11.0rc1

Provider hashicorp: 3.3.0rc1

Support multiple mount points in Vault backend secret (#29734): @hussein-awala

Provider mysql: 4.0.2rc1

Use MariaDB client binaries in arm64 image for support MySQL backend (#29519): @Taragolis

Provider sftp: 4.2.4rc1

Fix SFTPSensor when using newer_than and there are multiple matched files (#29794): @hussein-awala

Provider ssh: 3.5.0rc1

SSH Provider: Add cmd_timeout to ssh connection extra (#29347): @Aakcht

Provider telegram: 4.0.0rc1

Updated Telegram Provider to ensure compatbility with >=20.0.0 (#28953): @maxnathaniel

Provider yandex: 3.3.0rc1

support Yandex SDK feature "endpoint" (#29635): @s0neq

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

I acknowledge that I am a maintainer/committer of the Apache Airflow project.

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

@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!

@dominikhei

Use MariaDB client binaries in arm64 image for support MySQL backend #29519, checked if system have pre-installed client binaries for MySQL/MariaDB, than provider might be installed into the ARM. (note: Airflow on ARM is still experimental feature)
Use waiters in ECS Operators instead of inner sensors #29761: Test locally, work as expected, and no problem with aws_conn_id which is not set to default one "aws-default". cc: @dominikhei this change fix problem that you described in Airflow ECS Register Task Operator, error when passing env. variables #29504, if you would like, you also could test this Amazon Provider package

Checked flink -> it has the right >= 5.1.0 requirement on cncf.kubernetes 👍
Checked google -> the constants from auth library are properly inlined 👍

Looks good.

I checked apache-airflow-providers-amazon and the change in #29708 is working as expected.

Provider telegram: 4.0.0rc1 works as expected 👍

#29657 #29348 and #29364 Looks good

#29659 working 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.

@eladkal

#29741, #29699, and #29549 look good.
Thanks for organizing @eladkal!

#29623 working as expected.

#29680 is effectively a noop (for now) and it is working as expected :)

#29136 Has been tested with real Google Cloud resources successfully.

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.

#29434 has a unit test and also I use the same code locally in a while.

Navigation Menu

Repository navigation

Status of testing Providers that were prepared on March 03, 2023 #29901

Body

Provider amazon: 7.3.0rc1

Provider apache.flink: 1.0.1rc1

Provider apache.livy: 3.3.0rc1

Provider atlassian.jira: 2.0.1rc1

Provider cncf.kubernetes: 5.2.2rc1

Provider common.sql: 1.3.4rc1

Provider dbt.cloud: 3.1.0rc1

Provider github: 2.2.1rc1

Provider google: 8.11.0rc1

Provider 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

Committer

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Status of testing Providers that were prepared on March 03, 2023 #29901

Description

Body

Provider amazon: 7.3.0rc1

Provider apache.flink: 1.0.1rc1

Provider apache.livy: 3.3.0rc1

Provider atlassian.jira: 2.0.1rc1

Provider cncf.kubernetes: 5.2.2rc1

Provider common.sql: 1.3.4rc1

Provider dbt.cloud: 3.1.0rc1

Provider github: 2.2.1rc1

Provider google: 8.11.0rc1

Provider 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

Committer

Activity

eladkal commented on Mar 3, 2023

s0neq commented on Mar 3, 2023

vandonr-amz commented on Mar 3, 2023

fritz-astronomer commented on Mar 3, 2023

hussein-awala commented on Mar 3, 2023

eladkal commented on Mar 3, 2023

Aakcht commented on Mar 4, 2023

Taragolis commented on Mar 4, 2023

potiuk commented on Mar 4, 2023

pdebelak commented on Mar 4, 2023

maxnathaniel commented on Mar 4, 2023

pankajastro commented on Mar 6, 2023

romibuzi commented on Mar 6, 2023

raphaelauv commented on Mar 6, 2023

eladkal commented on Mar 6, 2023

josh-fell commented on Mar 6, 2023

pgagnon commented on Mar 6, 2023

IKholopov commented on Mar 6, 2023

kristopherkane commented on Mar 6, 2023

eladkal commented on Mar 6, 2023

LMnet commented on Mar 6, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions