[Draft - Do not merge] [Quantum] Add workspace MOBO storage account support (33346)

[warren-jones]

The quantum service will create a MOBO managed storage account during the workspace creation process.

Alternatively, the user may specify an existing storage account when creating a workspace. We are calling this "BYO storage account".

The CLI extension currently uses an ARM template to do workspace creation, but prior to CLI PR 4314 (February 2022) workspaces were created by calling the WorkspacesOperations.begin_create_or_update method of the extension’s control plane client. This code was simpler (and I think executed faster) than the ARM-template implementation.

I propose we revert to that implementation in the CLI instead of using an ARM template: CLI PR 4314 was a fix for an intermittent race condition between workspace creation, storage account creation, and role assignment, that were all initiated by the CLI code. Since the MOBO storage account will be created and managed in the service, this CLI race condition won’t happen. We can simplify the client side.

The CLI UX could be characterized as follows:

• Preferred usage: Don’t specify a SA – let the service create a MOBO SA
• If named in the command, the CLI will associate an existing “BYO” SA to the workspace (The existing ARM-template already does this as-is)
• These design alternatives need to be evaluated for when the user specifies a SA that doesn’t exist:

1. The CLI displays an error message directing the user to remove the SA-name parameter
2. The CLI creates a user-owned SA (The ARM-template does this as-is)
3. The CLI creates a user-owned SA only if the --byo-storage command parameter flag is present, otherwise it issues the error message

The third alternative would be a fail-safe for potential control plane problems with the MOBO feature. The CLI could fall back on the ARM-template code that has been in place since 2022.

Also, because the ARM-template implementation executes so slowly, leaving that code in place for BYO storage will incentivize the user to accept the [presumably] much faster MOBO storage account creation.

---

Related command

az quantum workspace create

---

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

[azure-client-tools-bot-prd]

⚠️Azure CLI Extensions Breaking Change Test

⚠️quantum

rule	cmd_name	rule_message	suggest_message
⚠️ 1006 - ParaAdd	quantum workspace create	cmd quantum workspace create added parameter byo_storage_account
⚠️ 1009 - ParaPropRemove	quantum workspace create	cmd quantum workspace create update parameter storage_account: removed property required=True

[azure-client-tools-bot-prd]

Hi @warren-jones,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[github-actions]

Hi @warren-jones

Release Suggestions

Module: quantum

• Please log updates into to src/quantum/HISTORY.rst
• Update VERSION to 1.0.0b7 in src/quantum/setup.py

Notes

• For more info about extension versioning, please refer to Extension version schema