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 and review the contribution guide to help.
Description
During azurerm_application_gateway deployment, changing the subnet_id of the gateway_ip_configuration causes the gateway to be stopped to allow the change to be appllied. This interaction is not obvious in the plan/apply logs, and results in the gateway being offline during the apply.
I'm not really sure what the idiomatic way of solving this would be, but either of thee following might be nice:
A warning about the stop/start behaviour in the plan output
An option in the provider features block to prevent the apply if it would result in a "stop" command being issued.
New or Affected Resource(s)/Data Source(s)
azurerm_application_gateway
Potential Terraform Configuration
provider"azurerm" {
features {
application_gateway {
prevent_stop_on_deployment=true
}
}
}
References
No response
The text was updated successfully, but these errors were encountered:
tony-harverson-moonpig
changed the title
Support for detecting/preventing "STOP" commands in apply on azurerm_application_gateway
Support for detecting/preventing "stop" commands on apply on azurerm_application_gateway
Nov 17, 2023
Is there an existing issue for this?
Community Note
Description
During azurerm_application_gateway deployment, changing the subnet_id of the gateway_ip_configuration causes the gateway to be stopped to allow the change to be appllied. This interaction is not obvious in the plan/apply logs, and results in the gateway being offline during the apply.
I'm not really sure what the idiomatic way of solving this would be, but either of thee following might be nice:
New or Affected Resource(s)/Data Source(s)
azurerm_application_gateway
Potential Terraform Configuration
References
No response
The text was updated successfully, but these errors were encountered: