You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Debug output may contain sensitive stuff to which I don't think I can share publicly.
Expected Behaviour
It should either accept that upper case characters is a valid name. Or, if this is a known Azure limitation, it should be documented as such that only lower case characters plus underscores are allowed in the container metadata.
Actual Behaviour
Error: MetaData must start with letters or an underscores. Got "noUpperCase".
on ../../_modules/container/main.tf line 9, in resource "azurerm_storage_container" "container":
9: resource "azurerm_storage_container" "container" {
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered:
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
locked as resolved and limited conversation to collaborators
Mar 28, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform (and AzureRM Provider) Version
Affected Resource(s)
azurerm_storage_container
Terraform Configuration Files
Where
metadata
looks something like thisDebug Output
Debug output may contain sensitive stuff to which I don't think I can share publicly.
Expected Behaviour
It should either accept that upper case characters is a valid name. Or, if this is a known Azure limitation, it should be documented as such that only lower case characters plus underscores are allowed in the container metadata.
Actual Behaviour
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: