Ekat/Quantum: Add new update job operation - #10161
Draft
v-elegacheva wants to merge 2 commits into
Draft
Conversation
Add support for updating a submitted job's name, priority, and tags via the new JobUpdateOptions merge-patch operation. Includes command registration, parameters, help, unit test, and version bump to 1.0.0b20.
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
microsoft-github-policy-service
Bot
requested review from
necusjz,
wangzelin007 and
yonzhan
July 30, 2026 17:49
microsoft-github-policy-service
Bot
added
the
customer-reported
Contributor
|
Thank you for your contribution @v-elegacheva! We will review the pull request and get back to you soon. |
microsoft-github-policy-service
Bot
added
Quantum
Member
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
v-elegacheva
marked this pull request as ready for review
July 30, 2026 18:09
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
There was a problem hiding this comment.
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 updatecommand wiring, parameters, and help content. - Implemented the
job_updateoperation 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. |
v-elegacheva
marked this pull request as draft
July 30, 2026 18:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new
az quantum job updatecommand 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-priorityis validated against thePriorityenum, at least one updatable field is required, and the refreshed job is returned. Note that--job-tagsreplaces the job's existing tags rather than appending.What Changed
az quantum job updatecommand, wired up with the workspace validator and job table transformer.--job-priorityand--job-tagsparameters