Azure / Azure/azure-cli-extensions

Issues for Azure Quantum

Open
#2,956 2 comments 0 reactions 1 assignee Claimed by @ricardo-espinoza View on GitHub
Quantum
Dominant language
Python
Stars
454
Forks
1.7k
Avg merge
2d 19h
Merged PRs (30d)
64

Description

- If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at [Azure/azure-cli](https://github.com/Azure/azure-cli/issues)

### Extension name (the extension in question)
Azure Quantum

### Description of issue (in as much detail as possible)
1.
In `submit()` method, there is a line
```
token = _get_data_credentials(cmd.cli_ctx, ws.subscription).get_token().token
```
I rarely see usage like this. Token of subscription is handled by Azure CLI framework. It will be put in Authorization header in HTTP request. Even extra tokens are handled well in Azure CLI. They will be put in x-ms-authorization-auxiliary header. We don't need to fetch and pass token manually in command implementation.

2.
```
Positional
: List of arguments expected by the Q# operation specified as --name=value
after `--`.
```
```
az quantum job submit -g fy -w w -l l --target-id t -- --a=b --b=c
```
I search `-- --` in Azure CLI and Azure CLI extension all examples and find no usage. Actually, I don't have suggestions on it. No requested change now.

-----

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.