-
Notifications
You must be signed in to change notification settings - Fork 98
Add support for workspace v2 endpoints #702
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…nly when not live
| WorkspaceName=(?P<workspace_name>[^\s;]+); | ||
| ApiKey=(?P<api_key>[^\s;]+); | ||
| QuantumEndpoint=(?P<quantum_endpoint>https://(?P<location>[^\s\.]+).quantum(?:-test)?.azure.com/); | ||
| QuantumEndpoint=(?P<quantum_endpoint>https://(?P<location>[^\s\.]+?)(?:-v2)?.quantum(?:-test)?.azure.com/); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since part of the reason to start discovering endpoints was to stop hardcoding them in the codebase. I think to that end, we could just verify that the overall URL structure is correct without hardcoding quantum,v2,azure.com in it. I understand that here we verify the connection string, but I don't know if we're gaining much by hardcoding the URL again here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's more about security: we are validating string coming from user environment which is used to generate a URL and fail fast if invalid data is detected
|
/azp run |
|
Commenter does not have sufficient privileges for PR 702 in repo microsoft/azure-quantum-python |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.