Skip to content

Upper bound azure-batch to avoid pulling in track 2 azure sdk changes#66455

Closed
amoghrajesh wants to merge 1 commit intoapache:mainfrom
amoghrajesh:fix/cap-azure-batch-below-15
Closed

Upper bound azure-batch to avoid pulling in track 2 azure sdk changes#66455
amoghrajesh wants to merge 1 commit intoapache:mainfrom
amoghrajesh:fix/cap-azure-batch-below-15

Conversation

@amoghrajesh
Copy link
Copy Markdown
Contributor

azure-batch 15.x which was released recently is a full rewrite that removes the older BatchServiceClient, batch_auth, and the other methods / call style that AzureBatchHook depends on. This needs to be capped to less than that version until the azure hook is rewritten / is migrated to BatchClient.


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

  • 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.

@wjddn279
Copy link
Copy Markdown
Contributor

wjddn279 commented May 6, 2026

@amoghrajesh

the same pr is already opened! could you see this?
#66452

@amoghrajesh
Copy link
Copy Markdown
Contributor Author

Closing in favour of #66452 (review)

@amoghrajesh amoghrajesh closed this May 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants