Skip to content
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

Support for extra info storageaccount name validation error #4932

Closed
sanderobdeijn opened this issue Nov 20, 2019 · 1 comment · Fixed by #5027
Closed

Support for extra info storageaccount name validation error #4932

sanderobdeijn opened this issue Nov 20, 2019 · 1 comment · Fixed by #5027

Comments

@sanderobdeijn
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

When creating a storage account name validation takes place and if the name isn't correct you get the following error:
Error: name can only consist of lowercase letters and numbers, and must be between 3 and 24 characters long

When using interpolation is it sometimes difficult to know what the used name was. Is it possible that the used name is shown in the error?

New or Affected Resource(s)

  • azurerm_storage_account

Potential Terraform Configuration

Not Applicable

References

Not Applicable

@ghost
Copy link

ghost commented Mar 29, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants