[Draft - Do not merge] [Quantum] Use Post Storage URI and SAS token like Quantum Python SDK

[warren-jones]

NOTE: Restore old version number before clicking "Ready for review"

The Azure Quantum CLI should use a Post Storage URI and a SAS token like Python SDK, azure-quantum-python.

Our CLI extension has a potential issue with directly using a user's credentials to access storage account to upload input or download output files, when our other SDK uses the PostStorageUri endpoint in our service. If we had the CLI extension use the same method, then we won't run into user permission issues with using CLI (if they have access to workspace, but not to storage account).

---

Related commands

az quantum job submit
az quantum execute
az run

---

• 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

️✔️Non Breaking Changes

[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]

Hi @warren-jones

Release Suggestions

Module: quantum

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

Notes

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