Do not update Azure resource if only AzApi-specific meta-properties are changed (e.g. retry, lock)

[cwe1ss]

Whenever we have to fine-tune the retry error messages, the locks-property (or any other AzAPI meta-property), all existing resources in all our terraform stacks show changes and execute updates to their underlying Azure APIs, even though nothing has actually changed about the resources. This is slow and results in many unnecessary Azure requests.

Is there any way for AzApi to fully ignore these changes (showing "No changes" in a terraform plan-step), or at least not execute a call to the underlying Azure API in the terraform apply-step?

[stemaMSFT]

Thanks for this issue @cwe1ss this does seem like a bug with the provider. Are you only fine-tuning for one resource and seeing changes across all the resources configured?

[cwe1ss]

It only affects the resource where we set it. But since we set the retry-property on many resources, and since we use our modules in many terraform stacks, it often results in many changes.

[stemaMSFT]

Gotcha! Have you set lifecycle ignore changes on the property?

lifecycle {
    ignore_changes = [retry, timeouts]
}

I know this adds more code, but it should suppress any state diff that is caused from this.

[cwe1ss]

Will using ignore_changes still use the most recent version of the set value in the next apply?

E.g., if I've initially set retry.error_message_regex to ["a"], and later change it to ["b"], will the next real apply use a or b?

[stemaMSFT]

Your next apply will not set the value to ["b"] as it will ignore updates to the resource property but still create with that property set (if specified): https://developer.hashicorp.com/terraform/language/meta-arguments/lifecycle#ignore_changes do you want to change the property's value but not have it show in state?

[ms-henglu]

Hi all,

I think it's better to improve the azapi's behavior that changing the azapi meta-properties won't trigger the http request.

[matt-FFFFFF]

See #745