Status of testing Providers that were prepared on May 05, 2025

[eladkal]

Body

I have a kind request for all the contributors to the latest provider distributions 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 comments, whether the issue is addressed.

These are providers that require testing as there were some substantial changes introduced:

Provider amazon: 9.7.0rc1

• Move SQS message queue to Amazon provider (#50057): @potiuk
• Fix typo in emr sensor (#49597): @o-nikolas
  Linked issues:
  • Linked Issue #49486: @ellisms
• Update prune_logs in Amazon provider package to support RuntimeTaskInstance (#49363): @vincbeck
• Remove AIRFLOW_2_10_PLUS conditions (#49877): @potiuk
• Bump min Airflow version in providers to 2.10 (#49843): @eladkal
• Update GlueJobOperator to inherit AWS base class (#49750): @ellisms
• Amazon EMR Sensors/Operators inherit AWS Base Classes (#49486): @ellisms
• Introduce lower bind to lxml as 5.4.0 (#49612): @amoghrajesh
• Remove Marshmallow from Core (#49388): @uranusjr

Provider apache.tinkerpop: 1.0.0rc1

• Create Apache TinkerPop provider (#47446): @ahmadtfarhan

Provider common.messaging: 1.0.1rc1

• Move SQS message queue to Amazon provider (#50057): @potiuk

Provider common.sql: 1.27.0rc1

• Fix SADeprecationWarning when using inspector with SQLAlchemy in DbApiHook (#48938): @dabla
• Fix: SQLExecuteQueryOperator does not pass extra_dejson values to hook_params (#49282): @kandharvishnu
• Refine type overload for common-sql (#50161): @guan404ming
  Linked issues:
  • Linked Issue #49334: @guan404ming
• Bump min Airflow version in providers to 2.10 (#49843): @eladkal
• Log generated SQL-statement and passed parameters as ERROR when insert_rows fails in DbApiHook (#48932): @dabla

Provider snowflake: 6.3.0rc1

• Adding OAuth support for SnowflakeHook (#47191): @Sharashchandra
  Linked issues:
  • Linked Issue #47073: @Sharashchandra
• Fix SnowflakeSqlApiHook backwards compatibility (#49482): @bugraoz93
  Linked issues:
  • Linked Issue #49449: @gopidesupavan
• make private_key_content in snowflake connection to be a base64 encoded string (#49467): @rawwar
• Fix mypy for get_oauth_token signature in SnowflakeSqlApiHook (#49449): @gopidesupavan
• Remove AIRFLOW_2_10_PLUS conditions (#49877): @potiuk
• Bump min Airflow version in providers to 2.10 (#49843): @eladkal
• Add logs SQL before execution in snowflake and databricks_sql (#48942): @guan404ming
  Linked issues:
  • Linked Issue #48688: @guan404ming
• Update deprecated functions to use the stable functions (#49460): @guan404ming
  Linked issues:
  • Linked Issue #49319: @brunocmartins

All users involved in the PRs:
@gopidesupavan @bugraoz93 @ellisms @o-nikolas @eladkal @uranusjr @rawwar @guan404ming @ahmadtfarhan @amoghrajesh @dabla @kandharvishnu @Sharashchandra @vincbeck @potiuk

Committer

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

[potiuk]

All good. Checked my changes, installed latest providers on latest airflow and the imports work nicely. @vincbeck -> I have not tested whether the "actual" AWS / common.messaging integration works after the move - I'd appreciate if you can test it too (do we have a system test for that one ?)

[potiuk]

Also min-versions look ok - including common.messaging with 3.0.1rc1 minimum version

[bugraoz93]

I have checked my changes, and it looks good! This check covers #49449, too, because those changes are in the same method. We can assume them as bundled change

[amoghrajesh]

My change this time: #49612 was just a CI fix. That looks good cos CI is stable :)

Even otherwise, ran couple of dags from my test suite, looks good.

[guan404ming]

I've verified all my changes and they looks good to me. I also add a test for my changes in common-sql in #50200 making sure the overload run correctly in runtime.

[Sharashchandra]

@eladkal I've checked my changes (#47191) and I see it's breaking. Changes from the following commit (c35afd1) is causing it to loop infinitely. The self.account_identifier property is calling the self._get_conn_params which inturn calls the get_oauth_token which again calls the self.account_identifier property.

[rawwar]

Tested #49467 and it is working

[eladkal]

@eladkal I've checked my changes (#47191) and I see it's breaking. Changes from the following commit (c35afd1) is causing it to loop infinitely. The self.account_identifier property is calling the self._get_conn_params which inturn calls the get_oauth_token which again calls the self.account_identifier property.

Can you raise PR to fix the bug?

[gopidesupavan]

@eladkal I've checked my changes (#47191) and I see it's breaking. Changes from the following commit (c35afd1) is causing it to loop infinitely. The self.account_identifier property is calling the self._get_conn_params which inturn calls the get_oauth_token which again calls the self.account_identifier property.

@eladkal looks like its issue, can we exclude from the release .

[potiuk]

Additionallly after my investigation (detailed) in #50285 (comment) -> I think we will have to release RC2 of amazon provider with limits removed from aiobotocore extra. The limits were added to avoid backtracking, but it's very likely they are not needed (let's see with #50285) and the problem is that new aiobotocore relased 5 days ago has different and conflicting limits and essentially it prevents installing aiobotcore+amazon+ constraints.

[eladkal]

@eladkal I've checked my changes (#47191) and I see it's breaking. Changes from the following commit (c35afd1) is causing it to loop infinitely. The self.account_identifier property is calling the self._get_conn_params which inturn calls the get_oauth_token which again calls the self.account_identifier property.

cc @bugraoz93 can you check this?
The report refrences your commit