Repository navigation
Closed
Labels
area:providerskind:metaHigh-level information important to the communityHigh-level information important to the communitytesting statusStatus of testing releasesStatus of testing releases
Description
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 airbyte: 5.2.3rc1
Provider amazon: 9.12.0rc1
- Add MwaaTaskSensor to Amazon Provider Package (#51719): @seanghaeli
- Support executor_config on Lambda Executor (#53994): @o-nikolas
- Fix AWS Lambda executor error handling for DLQ vs task failures (#53990): @isaiahiruoha
Provider apache.tinkerpop: 1.0.3rc1
Provider cncf.kubernetes: 10.7.0rc1
- Add support for taking the config file as a dict for KubernetesHook (#53126): @MaksYermak
- Kill kube watcher instance if it doesnt terminate gracefully in 60 seconds (#52662): @pavansharma36
Linked issues:
Provider common.sql: 1.27.5rc1
- Fix SnowflakeCheckOperator and SnowflakeValueCheckOperator to use parameters arg correctly (#53837): @gopidesupavan
Provider databricks: 7.7.1rc1
Provider edge3: 1.1.3rc1
- Fix: Prevent duplicate edge_job insertions for deferrable tasks in EdgeExecutor (#53610) (#53927): @Prasanth345
Provider fab: 2.4.0rc1
- Create HITL specific permission for core-API (#54043): @sjyangkevin
- fix: Add missing security settings for session cookie (#53542): @LipuFei
- Fix
Configmenu item missing inFabAuthManager(#53944): @vincbeck
Linked issues: - Add UI for human in the loop operators (#53035): @guan404ming
Linked issues:
Provider google: 17.1.0rc1
- Add Private Service Connect interface support to VertexAI operators (#54170): @MaksYermak
- Fix the google provider vertex_ai ImportDataOperator error (#53865): @olegkachur-e
- Google provider RayHook to proto compatibility (#54014): @olegkachur-e
- Fix the PostgresHook ignoring custom adapters registered (#53707): @olegkachur-e
Linked issues:
Provider microsoft.azure: 12.6.1rc1
Provider microsoft.winrm: 3.11.0rc1
Provider openlineage: 2.6.1rc1
- Allow secrets redact function to have different redaction than
***(#53977): @ashb
Linked issues: - Fix several deprecation warnings related to airflow.sdk (#53791): @Dev-iL
Provider postgres: 6.2.3rc1
Provider redis: 4.3.0rc1
- AIP-82: Add RedisPubSubMessageQueueProvider (#53556): @Jasperora
Linked issues:
Provider samba: 4.10.3rc1
Provider sftp: 5.3.4rc1
Provider slack: 9.1.4rc1
Provider smtp: 2.2.0rc1
- feat-51094: add OAuth 2 / XOAUTH2 support via
auth_type& token/credential extras (#53554): @nailo2c
Linked issues:
Provider snowflake: 6.5.2rc1
- Fix SnowflakeCheckOperator and SnowflakeValueCheckOperator to use parameters arg correctly (#53837): @gopidesupavan
Provider standard: 1.6.0rc1
- feat(htil): add
notifiersto HITLOperator (#54128): @Lee-W - feat(hitl): add HITLBranchOperator (#53960): @Lee-W
- feat(HITL): improve hitl trigger logging message (#53850): @Lee-W
- feat(hitl): add "timedout" column to HITLTriggerEventSuccessPayload (#53852): @Lee-W
- Restore
execute_completefunctionalityTimeSensorwhendeferrable=True(#53669): @jroachgolf84 - Fix several deprecation warnings related to airflow.sdk (#53791): @Dev-iL
- refactor(hitl): replace timezone usage with airflow.sdk.timezone (#53962): @Lee-W
- refactor(HITL): make default options class variables to avoid typo (#53849): @Lee-W
- Fix BranchPythonOperator documentation (#54205): @GrumpyCat51
Provider trino: 6.3.3rc1
- Added functionality to only allow one auth method simultaneously in the TrinoHook (#53134): @dominikhei
All users involved in the PRs:
@fritz-astronomer @Dev-iL @eladkal @Lee-W @gopidesupavan @dominikhei @isaiahiruoha @Prasanth345 @seanghaeli @vincbeck @jroachgolf84 @nailo2c @sjyangkevin @MaksYermak @LipuFei @Jasperora @GrumpyCat51
Committer
- I acknowledge that I am a maintainer/committer of the Apache Airflow project.
Metadata
Metadata
Assignees
Labels
area:providerskind:metaHigh-level information important to the communityHigh-level information important to the communitytesting statusStatus of testing releasesStatus of testing releases
Activity
LipuFei commentedon Aug 7, 2025
Hi @eladkal , #53542 works for me.
potiuk commentedon Aug 7, 2025
Did the PMC member verification all looks good. But I am -1 on standard. Repeating the arguments from devlist discussion:
Technically this is not a regression - because we have released it in 1.5.0 but we had #54124 (comment) that Pavan found and already fixed (I just merged) in #54214
Since this is affects PythonVirtualenv (badly), I think we should fix it rather quickly and have rc2 for standard provider (especially that the fix is already in)
gopidesupavan commentedon Aug 7, 2025
found one more issue, created latest package locally and ran example its giving me this error. it seems atleast the default python version needs to be set for uv.
Fix is coming..
gopidesupavan commentedon Aug 7, 2025
It affects mainly when UV is installed and here its default to auto to check https://github.com/apache/airflow/blob/main/providers/standard/src/airflow/providers/standard/utils/python_virtualenv.py#L48, i think its better to handle this setting default python version?
potiuk commentedon Aug 7, 2025
I think you should use "path to python" (that's what venv expects) - "python" is not a valid path ?
gopidesupavan commentedon Aug 7, 2025
nah this was failing to create venv given provided path, the command its running this one eg:
so here --python python is not recognising
pythonas valid interpreter. as per this https://docs.astral.sh/uv/reference/cli/#uv-python the request format we are using wrong? 🤔gopidesupavan commentedon Aug 7, 2025
okay i just ran that command in breeze it gives me this: so if the interpreter is set as python in system then there is no issue, otherwise its failing.
Should we default to some version or leave it as empty ? i think this error is valid if there is no interpreter configures then user should provide which python version they want use ?
aaron-y-chen commentedon Aug 8, 2025
I've tested my part on my local device, looking good!
potiuk commentedon Aug 8, 2025
Let's take it offline :) -> I don't think that is a "bug" - possibly an improvement in diagnostics/defaults :)
Prasanth345 commentedon Aug 8, 2025
Hi @eladkal , #53927, Tested the fix for duplicate edge_job insertions in edge3 provider (v1.1.3). Everything is working as expected — no issues found.
Lee-W commentedon Aug 8, 2025
Tested
apache-airflow-providers-standard==1.5.0withapache-airflow==3.0.4rc2.If a dag does not have HITLOperator, it works as expected. If a dag contains HITLOperators, it failed as expected.
I'd like to point out that a dag containing HITLOperators with Airflow < 3.1 kills the dag processor due to
AirflowOptionalProviderFeatureExceptionnot caught inairflow/airflow-core/src/airflow/dag_processing/processor.py
Lines 123 to 141 in dc952f0
or should we change it to
ImportErrorinsteadolegkachur-e commentedon Aug 8, 2025
Checked the #53707, #53865, #54014, all looks good.
pierceroberts commentedon Aug 8, 2025
@eladkal Anything I need to do specifically for #51503?
It's adding a few debug logs and updating a test.
The pipeline passed and tests passed locally.
gopidesupavan commentedon Aug 8, 2025
Verified my changes LGTM.
jason810496 commentedon Aug 9, 2025
There are still some concerns regarding the Redis provider that need to be discussed for AIP-82: Add RedisPubSubMessageQueueProvider, related dicussion #53556 (review) .
We might need to exclude Redis Provider for this batch release.
cc @eladkal
sjyangkevin commentedon Aug 10, 2025
The following tests have been done for #54043. In 3.1.0+, should be good, but some caveats we can have a look into it.
CC: @Lee-W , @guan404ming
Unit Test
HITL-related permission test


other tests related to fab/auth_manager
Airflow Manual Functional Test
In Airflow < 3.1.0, DAG processor will not start when there is a HITL DAG.

In Airflow 3.1.0+
Initialization
Test without permission, access is forbidden


Test with permission, access is good task can be triggered, but pop up


409 Conflicteven task can be successfully run.DAG is executed successfully if a user is assigned both edit permission to DAG and HITL_Detail resource

eladkal commentedon Aug 11, 2025
Thank you everyone. Providers are released.
Providers Standard and Redis are excluded from this release
I invite everyone to help improve providers for the next release, a list of open issues can be found here.