Null_resource with a destroy provisioner being destroyed for every trigger change

[Carles-Figuerola]

We have a null_resource provisioner with two local-exec (one with when = "destroy" ) and several triggers. Whenever one of the triggers changes (or shows known after apply) the null_resource is marked as must be replaced and seems to run the destroy provisioner and then the create provisioner, whereas I would expect that only the create provisioner would be run.

Is there a way to skip the destroy provisioner to run for every change of a null_resource?

Similar topics without an answer:

Null Resource create new resource without destroying original

I have a tf file that includes several resources and a null resource to run a script that creates a region specific configuration in AWS. I want to be able to change the variable for the aws region and have terraform create all new resources. For everything except the null resource that seems to work fine. But the null resource insists on destroying before creating the new resource in the new region. Is there a way to make terraform just leave the original resource and create the new one. I’d li…

[Carles-Figuerola]

another similar topic to this question:

Update a null_resource

There is currently a bug with the azurerm frontdoor resource so I’m working around it using null_resource to call az cli scripts. At the moment I’m working on the ability to create, update and delete a routing rule in front door. So far it looks something like this. resource "null_resource" "frontdoor_routing_rule" { triggers = { "routingRuleName" = var.frontdoor_routing_rule_name "frontDoorName" = var.frontdoor_name "resourceGroup" = var.frontdoor_resource_group …