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
ideally the child resource http_listener (name: httplistner1) was already created and when i try to add new listener , terraform should create only new listener which was added in input file
Actual Behaviour
ideally the child resource http_listener (name: httplistner1) was already created and when i try to add new listener , terraform force recreating the child resource http_listener (name: httplistner1).
Steps to Reproduce
No response
Important Factoids
No response
References
As per GitHub issue #6896 , its was fixed in PR #15800.
I still see it in azurerm 3.29.0 and 3.58.0 (latest)
The text was updated successfully, but these errors were encountered:
I am aware this is confusing and know this is not something you'd like to see. Fortunately, the call towards Azure APIs would contain the same information as if there was only a HTTP listener added, as it is just one call with both listeners in the body. I'm unaware that the order of HTTP listeners is influencing the (re)creation of a listener.
yes its causing downtime for those application onboarded on this appgw. Along with http_listener below child resources also has same behavior. Do you know the workaround ?
backend_http_settings
http_listener
request_routing_rule
ssl_certificate
A possible solution could be to make sure the oldest/existing child resources are first in the list, but I'm not sure if that influences anything. There is no other option I could think of.
TBH, I think this issue is a duplicate of #16136, and behaviour will therefore probably not change until v4.0.0 is in the picture.
Is there an existing issue for this?
Community Note
Terraform Version
1.3.2
AzureRM Provider Version
3.29.0
Affected Resource(s)/Data Source(s)
azurerm_application_gateway
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
ideally the child resource http_listener (name: httplistner1) was already created and when i try to add new listener , terraform should create only new listener which was added in input file
Actual Behaviour
ideally the child resource http_listener (name: httplistner1) was already created and when i try to add new listener , terraform force recreating the child resource http_listener (name: httplistner1).
Steps to Reproduce
No response
Important Factoids
No response
References
As per GitHub issue #6896 , its was fixed in PR #15800.
I still see it in azurerm 3.29.0 and 3.58.0 (latest)
The text was updated successfully, but these errors were encountered: