Skip to content

Quantum Add 'az quantum suite-offers target list' to list provider-account targets and status - #10194

Draft
v-elegacheva wants to merge 1 commit into
Azure:mainfrom
v-elegacheva:ekat/quantum-target-list-provider-account
Draft

Quantum Add 'az quantum suite-offers target list' to list provider-account targets and status#10194
v-elegacheva wants to merge 1 commit into
Azure:mainfrom
v-elegacheva:ekat/quantum-target-list-provider-account

Conversation

@v-elegacheva

@v-elegacheva v-elegacheva commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

🤖 PR Validation — ⚠️ Review suggested

Breaking Changes
⚠️ None
⚠️Azure CLI Extensions Breaking Change Test
⚠️quantum
rule cmd_name rule_message suggest_message
⚠️ 1011 - SubgroupAdd quantum suite-offers sub group quantum suite-offers added

Summary

Adds a new command for admin/research-lead users who operate in a provider-account (suite offer) context rather than a workspace.
az quantum suite-offers target list lists a provider account's targets and their status without requiring a workspace.

What changed

  • New command az quantum suite-offers target list -p <providerId> [-l <location>] in a new suite-offers target command group.
  • --location/-l is optional; when omitted it is resolved automatically from the provider account's suite offer.
  • Provider-account status is read from the V2 regional data plane (.../suiteoffers/{providerId}/providerStatus) by reusing the generated client's authenticated pipeline via send_request .
  • Version bumped to 1.0.0b21 with a HISTORY.rst entry.

@azure-pipelines

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

@a0x1ab

Copy link
Copy Markdown
Member

/azp run

@v-elegacheva v-elegacheva changed the title [Quantum] Add --provider-id to 'az quantum target list' for provider-… Quantum: Add --provider-id to 'az quantum target list' for provider-… Aug 7, 2026
@azure-pipelines

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

@v-elegacheva
v-elegacheva force-pushed the ekat/quantum-target-list-provider-account branch from e69a881 to c8de307 Compare August 10, 2026 20:57
@v-elegacheva
v-elegacheva marked this pull request as ready for review August 10, 2026 20:59
Copilot AI lite review requested due to automatic review settings August 10, 2026 20:59
@azure-pipelines

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

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR extends the quantum Azure CLI extension with a new provider-account (suite offer) target listing flow that doesn’t require an Azure Quantum workspace, and bumps the extension version/release notes accordingly.

Changes:

  • Adds a new command: az quantum suite-offers target list, wired to a new suiteoffers operations module and reusing the existing transform_targets table output.
  • Introduces data-plane support for provider-account status via a custom request (cf_provider_account_status) and V2 regional base URL handling.
  • Updates versioning artifacts (setup.py, HISTORY.rst) and adds unit tests covering response normalization/transform behavior.

Reviewed changes

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

Show a summary per file
File Description
src/quantum/setup.py Bumps extension version to 1.0.0b21.
src/quantum/HISTORY.rst Adds release notes for the new suite-offers target listing command.
src/quantum/azext_quantum/tests/latest/test_quantum_targets.py Adds unit tests for provider-account target listing normalization and transformer shape.
src/quantum/azext_quantum/operations/suiteoffers.py Implements list_targets and provider-account location resolution using suite offer listing.
src/quantum/azext_quantum/commands.py Registers the new quantum suite-offers target list command.
src/quantum/azext_quantum/_params.py Adds --provider-id and optional --location for quantum suite-offers target list.
src/quantum/azext_quantum/_help.py Adds help text and examples for the new suite-offers command group.
src/quantum/azext_quantum/_client_factory.py Adds base_url_v2, suite-offers mgmt client factory, and provider-account status request helper.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread src/quantum/azext_quantum/commands.py
@v-elegacheva v-elegacheva changed the title Quantum: Add --provider-id to 'az quantum target list' for provider-… Quantum Add 'az quantum suite-offers target list' to list provider-account targets and status Aug 10, 2026
@yonzhan

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

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

@v-elegacheva
v-elegacheva force-pushed the ekat/quantum-target-list-provider-account branch from c8de307 to 33c2a43 Compare August 11, 2026 17:44
@v-elegacheva
v-elegacheva marked this pull request as draft August 11, 2026 18:11
@v-elegacheva
v-elegacheva force-pushed the ekat/quantum-target-list-provider-account branch from 33c2a43 to db3d9a3 Compare August 11, 2026 18:32
@v-elegacheva
v-elegacheva marked this pull request as ready for review August 11, 2026 18:43
@azure-pipelines

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

@v-elegacheva
v-elegacheva force-pushed the ekat/quantum-target-list-provider-account branch from db3d9a3 to 805e7fd Compare August 11, 2026 20:35
Comment thread src/quantum/azext_quantum/operations/suiteoffers.py Outdated
Comment thread src/quantum/azext_quantum/_client_factory.py
Comment thread src/quantum/azext_quantum/_client_factory.py
"""
creds = _get_data_credentials(cli_ctx, subscription)
client = WorkspaceClient(base_url_v2(location), creds)
request = HttpRequest(

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a reason why we don't use cf_quantum_mgmt(cli_ctx).suite_offers here instead of construction http request by ourselves?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well the suite_offers ( SuiteOffersOperations ) only generates list_by_subscription , which is an ARM call returning the static suite-offer catalog and there is no providerStatus operation in the mgmt SDK. providerStatus is a live data-plane endpoint served from the -v2. regional host, not ARM, so the ARM-bound mgmt client can't reach it. I reuse the data-plane WorkspaceClient 's authenticated pipeline (correct regional endpoint + audience) and send the single ungenerated request. If/ when the service adds providerStatus to the Swagger, we can regenerate and drop the custom request.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, so if you need to use providerStatus call to get targets availability it has different url that does not contain suiteOffers in it, see here https://github.com/Azure/azure-rest-api-specs/blob/5f39f28d8337b0a8021a7e104c9fb6994b4bcf49/specification/quantum/data-plane/Quantum/preview/2026-01-15-preview/quantum.json#L561

@v-elegacheva
v-elegacheva marked this pull request as draft August 11, 2026 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

act-codegen-extensibility-squad Auto-Assign Auto assign by bot customer-reported Issues that are reported by GitHub users external to the Azure organization. Quantum az quantum

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants