[Bernd Verst (berndverst)]

🤖 PR Validation — ️✔️ All clear

Breaking Changes	Suppressions
️✔️ None	️✔️ None

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

az durabletask scheduler failover-instance

Test-only follow-up to #10482.

• Add a genuine, sanitized recording with 99 HTTP interactions for an eastasia primary and a southeastasia partner, both Dedicated capacity 1.
• Enable the failover lifecycle in default offline playback instead of skipping it as live-only.
• Cover configuration create/show/update/delete, graceful promotion of the secondary, forced failover back to the original primary, and replication-role checks.
• Use generated LRO polling for cleanup, add cleanup-helper regressions, and update the test documentation.

No extension runtime code, dependencies, version, or extension-index changes are included. Failed diagnostic captures are excluded from this follow-up.

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? (pip install azdev required)
• My extension version conforms to the Extension version schema

The existing extension version is unchanged because this PR only adds test coverage and recordings.

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

N/A: this is an existing extension.

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.

Validation

Commands were run locally using the Azure CLI development virtual environment:

• python -m azdev test --discover --no-exitfirst azext_durabletask -a --tb=short -q - passed: 69 tests, no skips.
• python scripts\ci\test_index.py -q - passed: 9 tests run, including 2 checks skipped outside CI.
• python -m azdev style durabletask --pep8 --pylint - passed: pylint and flake8.
• python -m azdev linter durabletask --min-severity medium - passed.
• python -m azdev scan --confidence-level MEDIUM -d src\durabletask -r --include '*.py' '*.yaml' '*.md' '*.rst' '*.json' '*.cfg' --continue-on-failure - passed: no secrets detected.

The live recording also passed using python -m azdev test --series --live test_durabletask_failover_lifecycle_live -a --tb=short --show-capture=no before the test was renamed to test_durabletask_failover_lifecycle_recorded for normal playback. The successful scenario's temporary resource groups were deleted. A separate account-identifier audit of the recording passed; no real subscription, tenant, caller, or credential details are included.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).

[Copilot]

🟢 Approval recommended

No active review issues are reported for the test-only update enabling recorded failover playback.

No open issues 🎉

What changed in this PR

This test-only follow-up enables offline playback of the Durable Task cross-region failover lifecycle, without changing extension runtime code or dependencies.

Changes:

• Switch the scenario from live-only to recorded playback using East Asia and Southeast Asia, with replication-role checks after graceful and forced failover.
• Use generated long-running-operation polling for cleanup and add cleanup-helper regression tests.
• Update documentation with the recorded scenario’s coverage, regions, and re-recording command.

File	Description
src/​durabletask/​README.md	Documents recorded failover coverage and re-recording instructions.
src/​durabletask/​azext_durabletask/​tests/​latest/​test_recording_processors.py	Adds cleanup tests for polling, missing configurations, and unexpected errors.
src/​durabletask/​azext_durabletask/​tests/​latest/​test_durabletask_scenario.py	Enables recorded failover playback, checks role transitions, and updates cleanup.

_{Review effort: Balanced}

[x-engineering-agent]

Hi Bernd Verst (@berndverst),
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 pyproject.toml (or setup.py, if the extension has not migrated yet) as well.