Remove acr validator from scopemaps #11784
Conversation
ghost
added
the
There was a problem hiding this comment.
hey @LP0101
Thanks for this PR.
Taking a look through whilst this is one approach to solving the issue - removing this validation makes it possible for folks to specify empty (or incorrect) values, which can cause ambiguous errors in the API - as such rather than removing this could we add a new validator covering the Container Registry Scope instead?
Thanks!
| ValidateFunc: validate.ContainerRegistryName, | ||
| Type: schema.TypeString, | ||
| Required: true, | ||
| ForceNew: true, |
There was a problem hiding this comment.
rather than removing this, can we add a validator which includes the correct values here?
There was a problem hiding this comment.
Done, added in a new validator & tests for scope maps
|
This has been released in version 2.60.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.60.0"
}
# ... other configuration ... |
Remove incorrect validator from scopemaps, as mentioned in hashicorp#11783
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Remove incorrect validator from scopemaps, as mentioned in #11783