On-premises Key Vault will not resolve without period in suffix-keyvault-dns value
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 3.5k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 64
Description
### Describe the bug
I am using az cli 2.53.1 in the official Microsoft container. If I try to do:
```shell
az keyvault secret set --name --vault-name --value=
```
Then, az cli is unable to resolve my hostname. I previously passed in via
```shell
az cloud register -n AzureStackUser --endpoint-resource-manager $METADATA_HOST --suffix-keyvault-dns $KEYVAULT_SUFFIX_DNS
```
My keyvault suffix dns. It was set to:
```shell
vault.
```
I could not figure out why AzCLI kept reporting that the name could not be resolved. I had to add a period in front of .vault since apparently AzCLI does not append a period.
I think AzCLI should append a period. This would make it consistent with how storage endpoint works. As far as I can tell, that does not require a period.
### Related command
see above
### Errors
Errno -2. Name could not be resolved.
### Issue script & Debug output
Not able to provide. Airgapped.
### Expected behavior
AzCLI does not require a period.
### Environment Summary
azure-cli 2.53.1
core 2.53.1
telemetry 1.10
Dependencies:
msal 1.24.0b2
azure-mgmt-resource 23.1.0b2
### Additional context
Using Azure Stack Hub
Contributor guide
Assessment
This issue has not been assessed yet.