Skip to content

[Datafactory] Fix Azure/azure-cli-extensions#10001: az datafactory trigger start: Retry on provisioning error instead of failing immediately - #10002

Draft
a0x1ab with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-datafactory-trigger-start
Draft

[Datafactory] Fix Azure/azure-cli-extensions#10001: az datafactory trigger start: Retry on provisioning error instead of failing immediately#10002
a0x1ab with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-datafactory-trigger-start

Conversation

Copilot AI commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

az datafactory trigger start throws BadRequest: Resource cannot be updated during provisioning when the trigger (e.g. created via Terraform) hasn't finished internal provisioning. The CLI previously surfaced this opaque service error with no recovery path.

Changes

  • manual/custom.py — Overrides the generated datafactory_trigger_start with retry logic:

    • Catches HttpResponseError where the message contains "Resource cannot be updated during provisioning"
    • Retries up to 10 times with a 30-second delay (~5 min total), logging a warning each attempt
    • After max retries, raises a CLIError with an actionable message naming the trigger
    • All other errors are re-raised immediately without retry
  • manual/tests/latest/test_datafactory_trigger_start_unit.py — New unit tests covering: immediate success, retry-then-succeed, max-retry exhaustion → CLIError, non-provisioning errors bypass retry, --no-wait flag passthrough

  • HISTORY.rst / setup.py — Version bumped to 1.0.5

Related command

az datafactory trigger start

General Guidelines

  • Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
  • Have you run python scripts/ci/test_index.py -q locally? (azdev required; see .azure-pipelines/templates/azdev_setup.yml for the install command until azdev==0.2.11b1 is on PyPI)
  • My extension version conforms to the Extension version schema

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

@azure-client-tools-bot-prd

azure-client-tools-bot-prd Bot commented Jun 22, 2026

Copy link
Copy Markdown
️✔️Azure CLI Extensions Breaking Change Test
️✔️Non Breaking Changes

@azure-client-tools-bot-prd

Copy link
Copy Markdown

Hi @copilot,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

Copilot AI changed the title [WIP] Fix unable to start datafactory trigger using az cli [Datafactory] Fix Azure/azure-cli-extensions#10001: az datafactory trigger start: Retry on provisioning error instead of failing immediately Jun 22, 2026
Copilot AI requested a review from a0x1ab June 22, 2026 17:01
@yonzhan

yonzhan commented Jun 23, 2026

Copy link
Copy Markdown
Collaborator

Datafactory

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants