Open lazarillo opened 3 years ago
OMG!!!
I finally figured out the problem: container_server
is an invalid name for a Key Vault secret. No underscores are allowed.
Wow!! I REALLY wish this were documented somewhere. Or even better, if MS can stop creating arbitrary naming restrictions. I cannot understand why the name of a secret needs any limitation, apart from possibly no spaces.
Key Vault Secrets
Issue Details
I am not sure what the problem is. I have a template that creates a few resources, then a key vault, then tries to save some of the output of the resources to the key vault as secrets. It is this secret save that was failing.
So I shortened the template to try to find the root cause, until I was left with just:
keyvault.json
:The key vault already exists. I have set the access policy to give me (my AD user ID) full authority for all secrets on the vault, and there is no network firewall, it is open.
Then I run, on the CLI:
This is as bare-bones as I can imagine. Everything else is working, except for the secrets, which I have shrunk down to the template shown above.
I keep getting the following unfortunately useless error:
Empty message, unhelpful "BadRequest" code. :(
Any ideas what is happening? There is no other possible security issue that could be blocking it. I am able to upload secrets myself via the portal. I am able to launch other services, so I think my IAM credentials should be fine.