[ML] Deployment templates bug fixes

[PratibhaShrivastav18]

---

Fix az ml deployment-template update crash and list table output
Bug Fixes -

• az ml deployment-template update — Fixed KeyError: 'tags' crash when updating a deployment template that has no tags or description. Changed bracket access to.get() for optional fields. SDK doesn't throw error in any immutable entity update scenario, keeping that behaviour same.

• az ml deployment-template list — Fixed -o table rendering empty output (no data rows). Added missing table_transformer for the list command.

Files Changed -

• deployment_template.py — Use parameters.get() instead of parameters[] for optional fields
• _format.py — Added transform_deployment_template_list
• commands.py — Wired table transformer to list command
• CHANGELOG.rst — Added v2.41.2 entry

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

Related command

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 wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

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

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]

Validation for Breaking Change Starting...

Thanks for your contribution!

[azure-client-tools-bot-prd]

Hi @PratibhaShrivastav18,
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.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

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).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[Copilot]

Pull request overview

This PR targets bug fixes in the machinelearningservices extension around deployment template commands, specifically stabilizing update when optional fields are missing and restoring usable -o table output for list.

Changes:

• Avoid KeyError in az ml deployment-template update when tags/description are absent.
• Add a table transformer for az ml deployment-template list and wire it into the command registration.
• Document the fixes in the extension changelog.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
src/machinelearningservices/azext_mlv2/manual/custom/deployment_template.py	Adjusts update logic to avoid KeyError for missing optional fields.
src/machinelearningservices/azext_mlv2/manual/commands.py	Registers a table_transformer for ml deployment-template list.
src/machinelearningservices/azext_mlv2/manual/_format.py	Introduces transform_deployment_template_list for table output formatting.
src/machinelearningservices/CHANGELOG.rst	Adds an Unreleased entry describing the fixes.

[github-actions]

Hi @PratibhaShrivastav18

Release Suggestions

Module: machinelearningservices

• Please log updates into to src/machinelearningservices/HISTORY.rst
• Update VERSION to 2.41.2 in src/machinelearningservices/setup.py

Notes

• For more info about extension versioning, please refer to Extension version schema

[yonzhan]

Please fix CI issues

[PratibhaShrivastav18]

@yonzhan I don't see any CI issues in the PR now.