[Workload-Orchestration] Added Context-ID in Target Update

[atharvau]

---

Fix contextId handling in workload-orchestration target commands

Summary

This PR addresses critical issues with contextId parameter handling in the workload-orchestration extension's target create and update commands, ensuring proper Azure resource management workflows.

Changes Made

1. Added required context-id parameter to target create command

• Added --context-id parameter as a required argument for target creation
• Ensures all targets are properly associated with their execution context
• Prevents creation of orphaned target resources

2. Fixed target update command contextId preservation

• Problem: The target update command was failing with ObjectMissingRequiredProperty: contextId errors
• Root Cause: The AAZ update operation follows a READ → PATCH → PUT pattern, but the contextId property was being dropped from the PUT payload due to missing schema definition
• Solution: Added contextId property to the target schema in _UpdateHelper._build_schema_target_read() method
• Impact: Target update operations now properly preserve the contextId during round-trip operations

Technical Details

• Modified _update.py to include contextId in the target resource schema
• Added proper serialization mapping (serialized_name="contextId")
• Marked as required field (flags={"required": True})
• Ensures compatibility with Azure Resource Manager requirements

Testing

• Verified target update commands no longer fail with contextId validation errors
• Confirmed contextId is preserved during update operations
• Tested with various target properties to ensure no regression

Test Evidence.pdf

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]

❌Azure CLI Extensions Breaking Change Test

❌workload-orchestration

rule	cmd_name	rule_message	suggest_message
❌ 1008 - ParaPropAdd	workload-orchestration target create	cmd workload-orchestration target create update parameter context_id: added property required=True	please remove property required=True for parameter context_id of cmd workload-orchestration target create
⚠️ 1009 - ParaPropRemove	workload-orchestration target create	cmd workload-orchestration target create update parameter description: removed property required=True

[azure-client-tools-bot-prd]

Hi @atharvau,
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>

[github-actions]

CodeGen Tools Feedback Collection

Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey

[github-actions]

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

[Copilot]

Pull Request Overview

This PR addresses critical contextId handling issues in the workload-orchestration extension's target commands and updates documentation/packaging. The changes ensure proper Azure resource management workflows by fixing parameter requirements and schema definitions.

Key changes include:

• Fixed target update command to preserve contextId during round-trip operations by adding it to the schema
• Made context-id parameter required for target create operations
• Updated package version to 2.0.0 with enhanced documentation and metadata

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
setup.py	Version bump to 2.0.0, status change to stable, and enhanced package description
_update.py	Added contextId to target schema and fixed provider namespace casing
_create.py	Made context-id parameter required and fixed provider namespace casing
README.md	Added comprehensive documentation about workload orchestration features
HISTORY.rst	Added changelog entry for version 2.0.0

Comments suppressed due to low confidence (2)

[necusjz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[theshubhamp]

revert?

[theshubhamp]

nit: extra line

[azclibot]

[Release] Update index.json for extension [ workload-orchestration-2.0.0 ] : https://dev.azure.com/msazure/One/_build/results?buildId=130825035&view=results