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
Run terraform plan and see a No changes, infrastructure up-to-date message. Or, at least in the following terraform plan after the terraform apply command has been fully executed.
Actual Behavior
When running terraform plan terraform keeps outputs actions where it's trying to re-create these blocks (we have other dynamic blocks configured pretty much with the same layout within the same resource, that don't give these issues), even after terraform apply is executed the following terraform plan output will be the same. The only difference I noticed is that if I leave only 1 block of this type and run terraform apply by allowing it to remove the existing blocks, and then run terraform plan again, it will then confirm that there are no changes, but as soon as I add again even one more block to the configuration, it will create it but then terraform plan will always output the destruction of the existing blocks, followed by a re-creation.
With this output, when runnin terraform apply the modification on the app_gateway resource takes 2 seconds, which I'm sure means that terraform actually doesn't do anything on the resource in this case (which is also confirmed by the fact that terraform keeps trying to do the same thing with every terraform plan/apply test).
Taking a look through this appears to be a duplicate of #6896 - rather than having multiple issues open tracking the same thing I'm going to close this issue in favour of that one; would you mind subscribing to #6896 for updates?
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!
ghost
locked as resolved and limited conversation to collaborators
Sep 30, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform (and AzureRM Provider) Version
v0.13.0
Affected Resource(s)
azurerm_application_gateway
Terraform Configuration Files
Expected Behavior
Run
terraform plan
and see a No changes, infrastructure up-to-date message. Or, at least in the followingterraform plan
after theterraform apply
command has been fully executed.Actual Behavior
When running
terraform plan
terraform keeps outputs actions where it's trying to re-create these blocks (we have other dynamic blocks configured pretty much with the same layout within the same resource, that don't give these issues), even afterterraform apply
is executed the followingterraform plan
output will be the same. The only difference I noticed is that if I leave only 1 block of this type and runterraform apply
by allowing it to remove the existing blocks, and then runterraform plan
again, it will then confirm that there are no changes, but as soon as I add again even one more block to the configuration, it will create it but then terraform plan will always output the destruction of the existing blocks, followed by a re-creation.With this output, when runnin
terraform apply
the modification on the app_gateway resource takes 2 seconds, which I'm sure means that terraform actually doesn't do anything on the resource in this case (which is also confirmed by the fact that terraform keeps trying to do the same thing with every terraform plan/apply test).Steps to Reproduce
request_routing_rule
block to the application gateway's configurationterraform plan -out filename
request_routing_rule
blockterraform apply filename
terraform plan
again and notice that terraform tries to do the same thing again, as ifterraform apply
hasn't actually done anything.The text was updated successfully, but these errors were encountered: