' azapi_resource ' resource does not support lifecycle meta argument

[mukulkapoor01-new]

A terraform apply is trying to destroy and re-create an existing Webapp in Azure because it detects a change in location, which is not the case. A lifecycle meta argument to ignore then changes in ' location ' could be useful in this scenario but ' azapi_resource ' does not support it.

Azapi version used: 1.15.0

[matt-FFFFFF]

I use azapi and it supports lifecycle meta argument:

see here

You should be able to ignore location changes like this:

resource "azapi_resource" "foo" {
  # ... other attributes
  lifecycle {
    ignore_changes = [location]
  }
}

Normally location is a top level attribute - are you trying to put it in the body?

[rmcolbert]

The "Microsoft.Web/sites/siteextensions" API doesn't support the top-level location attribute at all in the payload and it wasn't being used in the payload but the REST API response started injecting location (using full name, i.e. "East US 2" and not the shortname "eastus2").

Disabling built-in schema validation does allow the use of the ignore_changes = [location]

This feels like a backend management API issue that is bubbling up here but having location be a valid top level attribute on all API schemas (even if it gets thrown away internally) then we wouldn't need to disable schema validation.

[ms-henglu]

I'll close this issue in favor of #655 which also includes other resource types that have same issue.

Please subscribe to #655 for any updates. Thanks.