Skip to content

Conversation

@rigidit
Copy link
Contributor

@rigidit rigidit commented Nov 20, 2025

For workspace initialization from connection string, regex is updated to handle both v1 and v2 workspaces.

For non connection strings, if user provided resource id or params to build the resource id, we call ARM to fetch the workspace and get location and endpoint information. In case there is not enough params to build resource id, but workspace name is provided, we try to query ARG.

@rigidit rigidit changed the title Support v2 endpoints when creating workspace from connection string Workspace creation supports v2 endpoints Dec 2, 2025
@rigidit rigidit marked this pull request as ready for review December 11, 2025 00:16
@rigidit rigidit requested a review from a team as a code owner December 11, 2025 00:16
@rigidit rigidit changed the title Workspace creation supports v2 endpoints Add support for v2 endpoints in Workspace initialization Dec 11, 2025
@rigidit rigidit changed the title Add support for v2 endpoints in Workspace initialization Add support for workspace v2 endpoints Dec 11, 2025
@rigidit
Copy link
Contributor Author

rigidit commented Dec 11, 2025

/azp run

@azure-pipelines
Copy link

Commenter does not have sufficient privileges for PR 702 in repo microsoft/azure-quantum-python

@pavelbraginskiy
Copy link

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@rigidit rigidit requested a review from katymccl December 11, 2025 20:14
@rigidit rigidit requested a review from kikomiss December 11, 2025 20:14
WORKSPACE = "myworkspace"
LOCATION = "eastus"
STORAGE = "mystorage"
ENDPOINT_URI = f"https://{LOCATION}.quantum.azure.com/" # TODO change to f"https://{WORKSPACE}.{LOCATION}.quantum.azure.com/" when recordings are removed to follow format returned by ARM. Currently set to format which is used in connection string to avoid mass updates of recordings.

Check notice

Code scanning / devskim

A "TODO" or similar was left in source code, possibly indicating incomplete functionality Note test

Suspicious comment
@rigidit rigidit requested review from katymccl and kikomiss December 16, 2025 18:48
@kikomiss
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kikomiss kikomiss merged commit 0df2ac7 into microsoft:main Dec 16, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants