-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
azurerm_route fails if name attribute contains a slash #6053
Comments
OK, I'll fix this. Found out that there's a validation rule which should be used. (The name must begin with a letter or number, end with a letter, number or underscore, and may contain only letters, numbers, underscores, periods, or hyphens.) |
Alright, tests have passed. Please get back to me if there's something to improve @tombuildsstuff :-) |
azurerm_route - add validation to routing table name and route name (#6053)
This has been released in version 2.7.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.7.0"
}
# ... other configuration ... |
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 👉 [email protected]. Thanks! |
Terraform (and AzureRM Provider) Version
Terraform v0.12.21
Affected Resource(s)
azurerm_v1.44.0_x4
Terraform Configuration Files
If you create a route which includes a slash character in its name, the API call gets corrupted.
Debug Output
Expected Behavior
If the name attribute is used, it should be safely URL encoded.
Actual Behavior
Due to missing encoding, the attribute name could lead to wrong URL components (e.g. a slash in its value is interpreted as path separator. Maybe that could be an injection issue, too.
The text was updated successfully, but these errors were encountered: