[acrcssc] Un-pin the cssc image version to let the latest cached image be picked by acr task infra automatically during task runs#9757
Conversation
…icked by task automatically
️✔️Azure CLI Extensions Breaking Change Test
|
|
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 the acrcssc Azure CLI extension to stop pinning a specific CSSC container image tag in the ACR Task YAML templates, so task runs can use the task infrastructure’s cached/latest CSSC image without requiring an extension release for each image patch.
Changes:
- Bump extension version to
1.0.0b7and add release notes. - Remove the pinned
mcr.microsoft.com/acr/cssc:<tag>reference from multiple ACR Task YAML templates (including the dry-run template).
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| src/acrcssc/setup.py | Version bump to 1.0.0b7. |
| src/acrcssc/HISTORY.rst | Add changelog entry describing the unpin behavior. |
| src/acrcssc/azext_acrcssc/templates/tmp_dry_run_template.yaml | Remove pinned CSSC image reference from template values. |
| src/acrcssc/azext_acrcssc/templates/task/cssc_trigger_workflow.yaml | Remove pinned CSSC image reference from workflow trigger task template. |
| src/acrcssc/azext_acrcssc/templates/task/cssc_scan_image.yaml | Remove pinned CSSC image reference from scan task template. |
| src/acrcssc/azext_acrcssc/templates/task/cssc_patch_image.yaml | Remove pinned CSSC image reference from patch task template. |
PR Description:
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)For new extensions:
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.jsonautomatically.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.