Propagate verify and botocore_config in AWS Batch triggers by KarshVashi · Pull Request #67508 · apache/airflow

KarshVashi · 2026-05-25T22:33:46Z

Batch triggers (BatchJobTrigger, BatchCreateComputeEnvironmentTrigger) did not forward
verify or botocore_config to the hook, so deferrable Batch operators silently dropped
custom SSL and botocore settings when polling AWS from the triggerer.

Follows the same pattern established in the Lambda trigger migration
(providers/amazon/src/airflow/providers/amazon/aws/triggers/lambda_function.py).

What this changes:

Adds **kwargs passthrough in both trigger __init__ methods so base-class params
(verify, botocore_config) reach AwsBaseWaiterTrigger
Updates both hook() methods to pass self.verify and self.botocore_config to
BatchClientHook
Updates operator defer sites to forward verify and botocore_config to the triggers
Converts BatchCreateComputeEnvironmentTrigger call from positional to keyword args
Adds test coverage for serialization and hook propagation of both triggers

Part of #35278

Was generative AI tooling used to co-author this PR?

Yes - Claude Code (Opus 4.6)

Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (apache#67876) → Features (mirrors the batch-triggers entry apache#67508). - databricks: Lock in workflow depends_on parent-key behavior (apache#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (apache#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (apache#66513) → Misc.

* Prepare provider documentation 2026-06-02 * Address review feedback on provider changelogs - amazon: move S3 transfer-operators fix (#67378, vincbeck) and EcsRunTaskOperator log-level fix (#67180, jscheffl) from Features to Bug Fixes; beautify the EksPodOperator entry (#65335). - google: beautify the idle/auto-stop TTL entry (#65653) — drop conventional-commit prefix. - openlineage: beautify the ProcessPoolExecutor self-heal entry (#67400). - edge3: reword the 3.8.0 note — the provider still supports Airflow 3.0+, only the execute-callback feature (#67679) needs 3.3+ (jscheffl); move the Swagger API docs entry (#67390) to Doc-only; beautify the team_name clarification (#66718). - apache/drill: move the flit.sdist housekeeping entry (#65861) to the excluded block to match the kafka convention (jscheffl). * Make apache/drill 3.3.3 a doc-only release The only non-excluded drill change in this wave was the flit.sdist housekeeping entry, which jscheffl asked to exclude — leaving an empty changelog. Promote the DAG-to-Dag wording change (#66153) into a Doc-only section so drill 3.3.3 ships as a legitimate doc-only release instead of an empty one. * Fold post-prep provider commits into changelogs Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (#67876) → Features (mirrors the batch-triggers entry #67508). - databricks: Lock in workflow depends_on parent-key behavior (#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (#66513) → Misc.

KarshVashi · 2026-05-25T22:33:46Z

Batch triggers (BatchJobTrigger, BatchCreateComputeEnvironmentTrigger) did not forward
verify or botocore_config to the hook, so deferrable Batch operators silently dropped
custom SSL and botocore settings when polling AWS from the triggerer.

Follows the same pattern established in the Lambda trigger migration
(providers/amazon/src/airflow/providers/amazon/aws/triggers/lambda_function.py).

What this changes:

Adds **kwargs passthrough in both trigger __init__ methods so base-class params
(verify, botocore_config) reach AwsBaseWaiterTrigger
Updates both hook() methods to pass self.verify and self.botocore_config to
BatchClientHook
Updates operator defer sites to forward verify and botocore_config to the triggers
Converts BatchCreateComputeEnvironmentTrigger call from positional to keyword args
Adds test coverage for serialization and hook propagation of both triggers

Part of #35278

Was generative AI tooling used to co-author this PR?

Yes - Claude Code (Opus 4.6)

Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (apache#67876) → Features (mirrors the batch-triggers entry apache#67508). - databricks: Lock in workflow depends_on parent-key behavior (apache#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (apache#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (apache#66513) → Misc.

* Prepare provider documentation 2026-06-02 * Address review feedback on provider changelogs - amazon: move S3 transfer-operators fix (#67378, vincbeck) and EcsRunTaskOperator log-level fix (#67180, jscheffl) from Features to Bug Fixes; beautify the EksPodOperator entry (#65335). - google: beautify the idle/auto-stop TTL entry (#65653) — drop conventional-commit prefix. - openlineage: beautify the ProcessPoolExecutor self-heal entry (#67400). - edge3: reword the 3.8.0 note — the provider still supports Airflow 3.0+, only the execute-callback feature (#67679) needs 3.3+ (jscheffl); move the Swagger API docs entry (#67390) to Doc-only; beautify the team_name clarification (#66718). - apache/drill: move the flit.sdist housekeeping entry (#65861) to the excluded block to match the kafka convention (jscheffl). * Make apache/drill 3.3.3 a doc-only release The only non-excluded drill change in this wave was the flit.sdist housekeeping entry, which jscheffl asked to exclude — leaving an empty changelog. Promote the DAG-to-Dag wording change (#66153) into a Doc-only section so drill 3.3.3 ships as a legitimate doc-only release instead of an empty one. * Fold post-prep provider commits into changelogs Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (#67876) → Features (mirrors the batch-triggers entry #67508). - databricks: Lock in workflow depends_on parent-key behavior (#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (#66513) → Misc.

KarshVashi · 2026-05-25T22:33:46Z

Batch triggers (BatchJobTrigger, BatchCreateComputeEnvironmentTrigger) did not forward
verify or botocore_config to the hook, so deferrable Batch operators silently dropped
custom SSL and botocore settings when polling AWS from the triggerer.

Follows the same pattern established in the Lambda trigger migration
(providers/amazon/src/airflow/providers/amazon/aws/triggers/lambda_function.py).

What this changes:

Adds **kwargs passthrough in both trigger __init__ methods so base-class params
(verify, botocore_config) reach AwsBaseWaiterTrigger
Updates both hook() methods to pass self.verify and self.botocore_config to
BatchClientHook
Updates operator defer sites to forward verify and botocore_config to the triggers
Converts BatchCreateComputeEnvironmentTrigger call from positional to keyword args
Adds test coverage for serialization and hook propagation of both triggers

Part of #35278

Was generative AI tooling used to co-author this PR?

Yes - Claude Code (Opus 4.6)

Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (apache#67876) → Features (mirrors the batch-triggers entry apache#67508). - databricks: Lock in workflow depends_on parent-key behavior (apache#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (apache#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (apache#66513) → Misc.

* Prepare provider documentation 2026-06-02 * Address review feedback on provider changelogs - amazon: move S3 transfer-operators fix (#67378, vincbeck) and EcsRunTaskOperator log-level fix (#67180, jscheffl) from Features to Bug Fixes; beautify the EksPodOperator entry (#65335). - google: beautify the idle/auto-stop TTL entry (#65653) — drop conventional-commit prefix. - openlineage: beautify the ProcessPoolExecutor self-heal entry (#67400). - edge3: reword the 3.8.0 note — the provider still supports Airflow 3.0+, only the execute-callback feature (#67679) needs 3.3+ (jscheffl); move the Swagger API docs entry (#67390) to Doc-only; beautify the team_name clarification (#66718). - apache/drill: move the flit.sdist housekeeping entry (#65861) to the excluded block to match the kafka convention (jscheffl). * Make apache/drill 3.3.3 a doc-only release The only non-excluded drill change in this wave was the flit.sdist housekeeping entry, which jscheffl asked to exclude — leaving an empty changelog. Promote the DAG-to-Dag wording change (#66153) into a Doc-only section so drill 3.3.3 ships as a legitimate doc-only release instead of an empty one. * Fold post-prep provider commits into changelogs Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (#67876) → Features (mirrors the batch-triggers entry #67508). - databricks: Lock in workflow depends_on parent-key behavior (#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (#66513) → Misc.

KarshVashi · 2026-05-25T22:33:46Z

Batch triggers (BatchJobTrigger, BatchCreateComputeEnvironmentTrigger) did not forward
verify or botocore_config to the hook, so deferrable Batch operators silently dropped
custom SSL and botocore settings when polling AWS from the triggerer.

Follows the same pattern established in the Lambda trigger migration
(providers/amazon/src/airflow/providers/amazon/aws/triggers/lambda_function.py).

What this changes:

Adds **kwargs passthrough in both trigger __init__ methods so base-class params
(verify, botocore_config) reach AwsBaseWaiterTrigger
Updates both hook() methods to pass self.verify and self.botocore_config to
BatchClientHook
Updates operator defer sites to forward verify and botocore_config to the triggers
Converts BatchCreateComputeEnvironmentTrigger call from positional to keyword args
Adds test coverage for serialization and hook propagation of both triggers

Part of #35278

Was generative AI tooling used to co-author this PR?

Yes - Claude Code (Opus 4.6)

Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (apache#67876) → Features (mirrors the batch-triggers entry apache#67508). - databricks: Lock in workflow depends_on parent-key behavior (apache#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (apache#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (apache#66513) → Misc.

* Prepare provider documentation 2026-06-02 * Address review feedback on provider changelogs - amazon: move S3 transfer-operators fix (#67378, vincbeck) and EcsRunTaskOperator log-level fix (#67180, jscheffl) from Features to Bug Fixes; beautify the EksPodOperator entry (#65335). - google: beautify the idle/auto-stop TTL entry (#65653) — drop conventional-commit prefix. - openlineage: beautify the ProcessPoolExecutor self-heal entry (#67400). - edge3: reword the 3.8.0 note — the provider still supports Airflow 3.0+, only the execute-callback feature (#67679) needs 3.3+ (jscheffl); move the Swagger API docs entry (#67390) to Doc-only; beautify the team_name clarification (#66718). - apache/drill: move the flit.sdist housekeeping entry (#65861) to the excluded block to match the kafka convention (jscheffl). * Make apache/drill 3.3.3 a doc-only release The only non-excluded drill change in this wave was the flit.sdist housekeeping entry, which jscheffl asked to exclude — leaving an empty changelog. Promote the DAG-to-Dag wording change (#66153) into a Doc-only section so drill 3.3.3 ships as a legitimate doc-only release instead of an empty one. * Fold post-prep provider commits into changelogs Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (#67876) → Features (mirrors the batch-triggers entry #67508). - databricks: Lock in workflow depends_on parent-key behavior (#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (#66513) → Misc.

KarshVashi · 2026-05-25T22:33:46Z

Batch triggers (BatchJobTrigger, BatchCreateComputeEnvironmentTrigger) did not forward
verify or botocore_config to the hook, so deferrable Batch operators silently dropped
custom SSL and botocore settings when polling AWS from the triggerer.

Follows the same pattern established in the Lambda trigger migration
(providers/amazon/src/airflow/providers/amazon/aws/triggers/lambda_function.py).

What this changes:

Adds **kwargs passthrough in both trigger __init__ methods so base-class params
(verify, botocore_config) reach AwsBaseWaiterTrigger
Updates both hook() methods to pass self.verify and self.botocore_config to
BatchClientHook
Updates operator defer sites to forward verify and botocore_config to the triggers
Converts BatchCreateComputeEnvironmentTrigger call from positional to keyword args
Adds test coverage for serialization and hook propagation of both triggers

Part of #35278

Was generative AI tooling used to co-author this PR?

Yes - Claude Code (Opus 4.6)

Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (apache#67876) → Features (mirrors the batch-triggers entry apache#67508). - databricks: Lock in workflow depends_on parent-key behavior (apache#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (apache#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (apache#66513) → Misc.

* Prepare provider documentation 2026-06-02 * Address review feedback on provider changelogs - amazon: move S3 transfer-operators fix (#67378, vincbeck) and EcsRunTaskOperator log-level fix (#67180, jscheffl) from Features to Bug Fixes; beautify the EksPodOperator entry (#65335). - google: beautify the idle/auto-stop TTL entry (#65653) — drop conventional-commit prefix. - openlineage: beautify the ProcessPoolExecutor self-heal entry (#67400). - edge3: reword the 3.8.0 note — the provider still supports Airflow 3.0+, only the execute-callback feature (#67679) needs 3.3+ (jscheffl); move the Swagger API docs entry (#67390) to Doc-only; beautify the team_name clarification (#66718). - apache/drill: move the flit.sdist housekeeping entry (#65861) to the excluded block to match the kafka convention (jscheffl). * Make apache/drill 3.3.3 a doc-only release The only non-excluded drill change in this wave was the flit.sdist housekeeping entry, which jscheffl asked to exclude — leaving an empty changelog. Promote the DAG-to-Dag wording change (#66153) into a Doc-only section so drill 3.3.3 ships as a legitimate doc-only release instead of an empty one. * Fold post-prep provider commits into changelogs Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (#67876) → Features (mirrors the batch-triggers entry #67508). - databricks: Lock in workflow depends_on parent-key behavior (#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (#66513) → Misc.

KarshVashi · 2026-05-25T22:33:46Z

Batch triggers (BatchJobTrigger, BatchCreateComputeEnvironmentTrigger) did not forward
verify or botocore_config to the hook, so deferrable Batch operators silently dropped
custom SSL and botocore settings when polling AWS from the triggerer.

Follows the same pattern established in the Lambda trigger migration
(providers/amazon/src/airflow/providers/amazon/aws/triggers/lambda_function.py).

What this changes:

Adds **kwargs passthrough in both trigger __init__ methods so base-class params
(verify, botocore_config) reach AwsBaseWaiterTrigger
Updates both hook() methods to pass self.verify and self.botocore_config to
BatchClientHook
Updates operator defer sites to forward verify and botocore_config to the triggers
Converts BatchCreateComputeEnvironmentTrigger call from positional to keyword args
Adds test coverage for serialization and hook propagation of both triggers

Part of #35278

Was generative AI tooling used to co-author this PR?

Yes - Claude Code (Opus 4.6)

Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (apache#67876) → Features (mirrors the batch-triggers entry apache#67508). - databricks: Lock in workflow depends_on parent-key behavior (apache#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (apache#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (apache#66513) → Misc.

* Prepare provider documentation 2026-06-02 * Address review feedback on provider changelogs - amazon: move S3 transfer-operators fix (#67378, vincbeck) and EcsRunTaskOperator log-level fix (#67180, jscheffl) from Features to Bug Fixes; beautify the EksPodOperator entry (#65335). - google: beautify the idle/auto-stop TTL entry (#65653) — drop conventional-commit prefix. - openlineage: beautify the ProcessPoolExecutor self-heal entry (#67400). - edge3: reword the 3.8.0 note — the provider still supports Airflow 3.0+, only the execute-callback feature (#67679) needs 3.3+ (jscheffl); move the Swagger API docs entry (#67390) to Doc-only; beautify the team_name clarification (#66718). - apache/drill: move the flit.sdist housekeeping entry (#65861) to the excluded block to match the kafka convention (jscheffl). * Make apache/drill 3.3.3 a doc-only release The only non-excluded drill change in this wave was the flit.sdist housekeeping entry, which jscheffl asked to exclude — leaving an empty changelog. Promote the DAG-to-Dag wording change (#66153) into a Doc-only section so drill 3.3.3 ships as a legitimate doc-only release instead of an empty one. * Fold post-prep provider commits into changelogs Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (#67876) → Features (mirrors the batch-triggers entry #67508). - databricks: Lock in workflow depends_on parent-key behavior (#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (#66513) → Misc.

KarshVashi · 2026-05-25T22:33:46Z

Batch triggers (BatchJobTrigger, BatchCreateComputeEnvironmentTrigger) did not forward
verify or botocore_config to the hook, so deferrable Batch operators silently dropped
custom SSL and botocore settings when polling AWS from the triggerer.

Follows the same pattern established in the Lambda trigger migration
(providers/amazon/src/airflow/providers/amazon/aws/triggers/lambda_function.py).

What this changes:

Adds **kwargs passthrough in both trigger __init__ methods so base-class params
(verify, botocore_config) reach AwsBaseWaiterTrigger
Updates both hook() methods to pass self.verify and self.botocore_config to
BatchClientHook
Updates operator defer sites to forward verify and botocore_config to the triggers
Converts BatchCreateComputeEnvironmentTrigger call from positional to keyword args
Adds test coverage for serialization and hook propagation of both triggers

Part of #35278

Was generative AI tooling used to co-author this PR?

Yes - Claude Code (Opus 4.6)

Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (apache#67876) → Features (mirrors the batch-triggers entry apache#67508). - databricks: Lock in workflow depends_on parent-key behavior (apache#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (apache#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (apache#66513) → Misc.

* Prepare provider documentation 2026-06-02 * Address review feedback on provider changelogs - amazon: move S3 transfer-operators fix (#67378, vincbeck) and EcsRunTaskOperator log-level fix (#67180, jscheffl) from Features to Bug Fixes; beautify the EksPodOperator entry (#65335). - google: beautify the idle/auto-stop TTL entry (#65653) — drop conventional-commit prefix. - openlineage: beautify the ProcessPoolExecutor self-heal entry (#67400). - edge3: reword the 3.8.0 note — the provider still supports Airflow 3.0+, only the execute-callback feature (#67679) needs 3.3+ (jscheffl); move the Swagger API docs entry (#67390) to Doc-only; beautify the team_name clarification (#66718). - apache/drill: move the flit.sdist housekeeping entry (#65861) to the excluded block to match the kafka convention (jscheffl). * Make apache/drill 3.3.3 a doc-only release The only non-excluded drill change in this wave was the flit.sdist housekeeping entry, which jscheffl asked to exclude — leaving an empty changelog. Promote the DAG-to-Dag wording change (#66153) into a Doc-only section so drill 3.3.3 ships as a legitimate doc-only release instead of an empty one. * Fold post-prep provider commits into changelogs Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (#67876) → Features (mirrors the batch-triggers entry #67508). - databricks: Lock in workflow depends_on parent-key behavior (#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (#66513) → Misc.

KarshVashi · 2026-05-25T22:33:46Z

Batch triggers (BatchJobTrigger, BatchCreateComputeEnvironmentTrigger) did not forward
verify or botocore_config to the hook, so deferrable Batch operators silently dropped
custom SSL and botocore settings when polling AWS from the triggerer.

Follows the same pattern established in the Lambda trigger migration
(providers/amazon/src/airflow/providers/amazon/aws/triggers/lambda_function.py).

What this changes:

Adds **kwargs passthrough in both trigger __init__ methods so base-class params
(verify, botocore_config) reach AwsBaseWaiterTrigger
Updates both hook() methods to pass self.verify and self.botocore_config to
BatchClientHook
Updates operator defer sites to forward verify and botocore_config to the triggers
Converts BatchCreateComputeEnvironmentTrigger call from positional to keyword args
Adds test coverage for serialization and hook propagation of both triggers

Part of #35278

Was generative AI tooling used to co-author this PR?

Yes - Claude Code (Opus 4.6)

Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (apache#67876) → Features (mirrors the batch-triggers entry apache#67508). - databricks: Lock in workflow depends_on parent-key behavior (apache#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (apache#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (apache#66513) → Misc.

* Prepare provider documentation 2026-06-02 * Address review feedback on provider changelogs - amazon: move S3 transfer-operators fix (#67378, vincbeck) and EcsRunTaskOperator log-level fix (#67180, jscheffl) from Features to Bug Fixes; beautify the EksPodOperator entry (#65335). - google: beautify the idle/auto-stop TTL entry (#65653) — drop conventional-commit prefix. - openlineage: beautify the ProcessPoolExecutor self-heal entry (#67400). - edge3: reword the 3.8.0 note — the provider still supports Airflow 3.0+, only the execute-callback feature (#67679) needs 3.3+ (jscheffl); move the Swagger API docs entry (#67390) to Doc-only; beautify the team_name clarification (#66718). - apache/drill: move the flit.sdist housekeeping entry (#65861) to the excluded block to match the kafka convention (jscheffl). * Make apache/drill 3.3.3 a doc-only release The only non-excluded drill change in this wave was the flit.sdist housekeeping entry, which jscheffl asked to exclude — leaving an empty changelog. Promote the DAG-to-Dag wording change (#66153) into a Doc-only section so drill 3.3.3 ships as a legitimate doc-only release instead of an empty one. * Fold post-prep provider commits into changelogs Incremental-update pass for commits that landed on main after this wave was prepared: - amazon: Propogate verify/botocore_config in redshift cluster triggers (#67876) → Features (mirrors the batch-triggers entry #67508). - databricks: Lock in workflow depends_on parent-key behavior (#66681) → Bug Fixes. - edge3: Fix Edge worker fork mode reporting supervisor failures as success (#67887) → Bug Fixes. - google: Migrate Stackdriver logging config to RemoteLogIO pattern (#66513) → Misc.

propogate verify and botocore_config in batch triggers
f5d3834

KarshVashi requested a review from o-nikolas as a code owner May 25, 2026 22:33

boring-cyborgBot added area:providers provider:amazon AWS/Amazon - related issues labels May 25, 2026

kaxil approved these changes May 25, 2026
View reviewed changes

kaxil merged commit 0a2f181 into apache:mainMay 25, 2026
94 checks passed

KarshVashi mentioned this pull request Jun 1, 2026
Propogate verify and botocore_config in redshift cluster triggers #67876
Merged
1 task

This was referenced Jun 3, 2026
Status of testing Providers that were prepared on June 02, 2026 #67957
Closed
Status of testing Providers that were prepared on June 08, 2026 #68225
Closed

This was referenced Aug 20, 2026
Use the operator's AWS settings for deferred SageMaker tasks #71857
Merged
Use the operator's AWS settings for deferred Neptune, MWAA, SSM tasks #72098
Open

o-nikolas mentioned this pull request Aug 26, 2026
Status of testing Providers that were prepared on August 25, 2026 #72117
Closed
12 tasks