Skip to content

remove depericated --location#9903

Draft
s-ddavydenko wants to merge 1 commit into
Azure:mainfrom
s-ddavydenko:main
Draft

remove depericated --location#9903
s-ddavydenko wants to merge 1 commit into
Azure:mainfrom
s-ddavydenko:main

Conversation

@s-ddavydenko
Copy link
Copy Markdown

@s-ddavydenko s-ddavydenko commented May 27, 2026

Summary

Removes the deprecated --location / -l parameter from az quantum job commands. Job operations now derive the workspace location from the active workspace (set via az quantum workspace set) instead of accepting an independent, easily-mismatched value from the user.

Motivation

--location on az quantum job was redundant — the location is already an intrinsic property of the target workspace. Allowing it to be passed independently meant a user could specify a region that didn't match their workspace, producing confusing failures downstream. The parameter was already marked deprecated and scheduled for removal.

Changes

  • Removed --location / -l from az quantum job command definitions and from the underlying operations/job.py functions.
  • Updated help text, examples, and the README to drop references to --location.
  • Submission code no longer mutates the caller's input_params dict; a local copy is used when defaults need to be injected.
  • Bumped extension version in setup.py; added entry to HISTORY.rst.

Testing

  • All unit tests in src/quantum/azext_quantum/tests/latest pass locally (pytest).
  • Live test_jobs exercised against a personal Azure Quantum workspace via AZURE_QUANTUM_* env vars; submit / list / show / cancel succeed without --location.
  • The remaining live-test failures observed locally (test_submit*, test_workspace_create_destroy, test_workspace_keys, test_get_provider, test_workspace, test_targets) are pre-existing and unrelated to this change:
    • AttributeError: 'QuantumWorkspace' object has no attribute 'providers' — SDK drift in operations/workspace.py (the regenerated SDK moved providers onto workspace.properties.providers).
    • The others depend on a Microsoft-internal e2e workspace (e2e-scenarios/qw-e2e-tests-eus) hard-coded in tests/latest/utils.py that isn't accessible from a personal subscription.
      Both reproduce on main.

@azure-client-tools-bot-prd
Copy link
Copy Markdown

Validation for Breaking Change Starting...

Thanks for your contribution!

@microsoft-github-policy-service microsoft-github-policy-service Bot added the Auto-Assign Auto assign by bot label May 27, 2026
@s-ddavydenko s-ddavydenko changed the title remove dpericated --location remove depericated --location May 27, 2026
@yonzhan yonzhan requested a review from necusjz May 27, 2026 23:40
@yonzhan
Copy link
Copy Markdown
Collaborator

yonzhan commented May 27, 2026

quantum

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Auto-Assign Auto assign by bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants