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
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
Terraform (and AzureRM Provider) Version
Affected Resource(s)
azurerm_application_gateway
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
redirect_configuration_name must not be set if either backend_address_pool_name or backend_http_settings_name are set. Validations should check for that during plan.
Actual Behavior
Since those validations are in the flatten functions the error is caught directly by Azure.
I'm opening a PR moving those validations to the corresponding expand function.
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 and limited conversation to collaborators
Jun 10, 2019
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_application_gateway
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
redirect_configuration_name must not be set if either backend_address_pool_name or backend_http_settings_name are set. Validations should check for that during plan.
Actual Behavior
Since those validations are in the flatten functions the error is caught directly by Azure.
I'm opening a PR moving those validations to the corresponding expand function.
The text was updated successfully, but these errors were encountered: