Skip to content

Move AwsToAwsBaseOperator fallback out of init - #70445

Merged
vincbeck merged 1 commit into
apache:mainfrom
fat-catTW:fix-aws-to-aws-base-operator-init
Jul 27, 2026
Merged

Move AwsToAwsBaseOperator fallback out of init#70445
vincbeck merged 1 commit into
apache:mainfrom
fat-catTW:fix-aws-to-aws-base-operator-init

Conversation

@fat-catTW

Copy link
Copy Markdown
Contributor

Move AwsToAwsBaseOperator destination connection fallback out of constructor logic so template fields are assigned verbatim during __init__.

Remove the fixed class from the operator-init exemption list and add regression coverage for default and explicit destination connection behavior.

related: #70296

Was generative AI tooling used to co-author this PR?
  • [X] Yes (please specify the tool below)

Generated-by: [Codex] following the guidelines


  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

@vincbeck
vincbeck merged commit 908115a into apache:main Jul 27, 2026
83 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-3-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 908115a v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants