-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pulumi complains that keyvault name does not comply, while it is accepted just fine by Azure #2532
Comments
Hi @ilya-scale Thank you for filing the issue and sorry for confusion. What happens here is that Pulumi generates an auto-name by default by appending a random 8-character suffix to the name, e.g. it becomes something like Two things you can do:
|
Is this intended and a feature? It seems a bit counter-intuitive that this happens by default. At least it does not happen in terraform. Or is the value that I have sent not connected to the real name of the resource, and corresponds to the id in the terraform that is used for state handling? Maybe there is also some option to use the name from id by default? It seems that for the secret itself it works this way - I have not specified the name, but it was created correctly P.S. It would probably be a good idea to include the name somewhere in the error response so that it will be obvious |
Yes, this is by design. Indeed, the name that you pass is a logical resource name in Pulumi, while the physical name is generated with a suffix by default, so that replacement operations could use create-before-delete semantics, for example. This is different from Terraform. Enhancements are tracked in pulumi/pulumi#1518
Definitely! Sounds like a great idea. |
Thanks a lot for clarification! |
What happened?
I tried to create a key vault with this name:
kv-some-update-dev (same for kv-some-updatedev)
It failed
error: azure-native:keyvault:Vault resource 'kv-some-updatedev' has a problem: 'vaultName' does not match expression '^[a-zA-Z0-9-]{3,24}$'
Expected Behavior
It should work
Steps to reproduce
Output of
pulumi about
Additional context
There was a similar error before but it seems it was fixed only partially
#1646
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: