Ekat/Quantum: Add new update job operation

[v-elegacheva]

🤖 PR Validation — ⚠️ Review suggested

Breaking Changes
⚠️ None

⚠️Azure CLI Extensions Breaking Change Test

⚠️quantum

rule	cmd_name	rule_message	suggest_message
⚠️ 1001 - CmdAdd	quantum job update	cmd quantum job update added

Summary

Adds a new az quantum job update command that lets users update a submitted job's name, priority, and/or tags after submission. This implements the CLI side of the merged Data Plane API Spec. Only the fields that user provides are sent in the patch, --job-priority is validated against the Priority enum, at least one updatable field is required, and the refreshed job is returned. Note that --job-tags replaces the job's existing tags rather than appending.

What Changed

• Added the az quantum job update command, wired up with the workspace validator and job table transformer.
• Implemented the update operation using the data-plane jobs client's merge-patch API, which builds the patch from only the provided fields, validated priority, requires at least one updatable field, and returns the refreshed job.
• Added the --job-priority and --job-tags parameters
• Added command help with examples for renaming, changing priority, and replacing tags.
• Bumped the extension version and updated the changelog.
• Added unit and live scenario test coverage for the new command and its parameters.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[microsoft-github-policy-service]

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

[a0x1ab]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

This PR introduces a new az quantum job update operation in the Quantum CLI extension, allowing users to update an existing job’s name, priority, and/or tags, and bumps the extension version accordingly.

Changes:

• Added az quantum job update command wiring, parameters, and help content.
• Implemented the job_update operation using the data-plane jobs client merge-patch update API and returning the refreshed job.
• Added unit and live scenario test coverage for the new command and bumped extension version/history.

Reviewed changes

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

Show a summary per file

File	Description
src/quantum/setup.py	Bumps extension version to 1.0.0b20.
src/quantum/HISTORY.rst	Adds release note entry for the new job update command.
src/quantum/azext_quantum/tests/latest/test_quantum_jobs.py	Adds unit test for job_update and a live scenario update call.
src/quantum/azext_quantum/operations/job.py	Implements job_update operation (merge-patch + refresh).
src/quantum/azext_quantum/commands.py	Registers quantum job update command with transformer/validator.
src/quantum/azext_quantum/_params.py	Adds --job-priority and --job-tags arguments for quantum job update.
src/quantum/azext_quantum/_help.py	Adds help and examples for az quantum job update.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated no new comments.

Suppressed comments (1)

src/quantum/azext_quantum/tests/latest/test_quantum_jobs.py:257

• The new live scenario block exercises --job-priority and --job-tags, but it only asserts that the job name changed. To make this a true end-to-end validation of the update behavior (and avoid a false positive if the service ignores priority/tags), also assert the returned priority and tags fields match the requested values.

        # Update the submitted job's name, priority, and tags, then confirm the change
        updated_job = self.cmd(f'az quantum job update -j {results["id"]} --job-name "Updated job name" --job-priority High --job-tags tag1 tag2 -o json').get_output_in_json()
        self.assertEqual(updated_job["name"], "Updated job name")

[a0x1ab]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.