{CI} Update references for generate/verify commandIdx to use azdev command#33121
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
There was a problem hiding this comment.
Pull request overview
This PR updates Azure CLI’s CI and contributor-facing references for generating/verifying the packaged “latest” index assets to use the azdev latest-index wrapper command instead of calling scripts/generate_latest_indices.py directly.
Changes:
- Update the mismatch remediation guidance in
scripts/generate_latest_indices.pyto referenceazdev latest-index generate. - Add contributor documentation for
azdev latest-index generate/verifyusage. - Switch the pipeline “Verify latest index assets” job to run
azdev latest-index verify.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| scripts/generate_latest_indices.py | Updates verify-mode “Run:” guidance to point to the azdev wrapper command. |
| doc/authoring_command_modules/README.md | Documents the new azdev latest-index generate/verify workflow and flags. |
| azure-pipelines.yml | Uses azdev latest-index verify --repo . in CI instead of running the Python script directly. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Related command
Description
This PR adds
azdevlatest-index generate and verify as the documented workflow for maintaining packaged latest index files, with explicit Azure CLI path support and CI-friendly verify behavior.It also updates CI and contributor guidance to use the new commands, and improves mismatch messaging to show either the
azdevfix path or the standalone script fallback.Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.