Graceful error for immutable field updates on deployment template#9849
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @PratibhaShrivastav18, |
|
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 aims to make az ml deployment-template update fail more clearly when callers try to modify immutable deployment-template fields, instead of allowing only metadata updates (description/tags) to proceed silently. It fits into the Azure ML CLI extension’s custom command layer for registry-scoped deployment template management.
Changes:
- Adds an immutable-field check in
_ml_deployment_template_updatebefore applying updates. - Restricts in-place updates to
descriptionandtags. - Simplifies mutable-field assignment by using direct indexed access for present parameters.
Release SuggestionsModule: machinelearningservices
Notes
|
b7c5e53 to
808488d
Compare
kshitij-microsoft
left a comment
There was a problem hiding this comment.
Please make sure to test this thoroughly, I remember running into some issues while using this notation.
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
The test cassettes had inconsistent 'stage' field values between the getter GET (Development) and the setter GET (Archived). This caused the immutable field validation to falsely detect a user change to the 'stage' field when only tags/description were being updated.
c590832
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
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.