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
With v2.0.1 this resulted in the following error: hasBgpOverride is not expected here, it's read only.
As this seems to be an error with the schema, we added schema_validation_enabled = false. This resulted in the following terraform plan:
Terraform will perform the following actions:# module.resolver.module.vnet_peering.azapi_resource.hub_gateway_route["0"] will be updated in-place
~ resource"azapi_resource""hub_gateway_route" {
id="/subscriptions/xyz/resourceGroups/rg-xyz/providers/Microsoft.Network/routeTables/rt-xyz/routes/udr-vnet-xyz-0"name="udr-vnet-xyz-0"
~ schema_validation_enabled=true->falsetags={}
# (7 unchanged attributes hidden)
}
Plan:0 to add, 1 to change, 0 to destroy.
The apply then failed with following error message:
Error: Provider produced inconsistent result after apply
When applying changes to module.resolver.module.vnet_peering.azapi_resource.hub_gateway_route["0"],
provider "provider[\"registry.terraform.io/azure/azapi\"]" produced an
unexpected new value: .output.etag: was
cty.StringVal("W/\"ff4b68ad-8519-421e-8284-94d34480545f\""), but now
cty.StringVal("W/\"1426bdd3-df9d-473f-83ae-5d1452ba46e2\"").
This is a bug in the provider, which should be reported in the provider's own issue tracker.
The text was updated successfully, but these errors were encountered:
In the 2.0, the output will default to the readonly properties. In above case, it will output the etag and etag gets updated when there're PUT requests to update the resource.
I'll work on improving this.
And I have some workarounds to help with this case:
When trying to upgrade from v1.14.0 to v2.0.1 we are having an issue with our
Microsoft.Network/routeTables/routes
-resource.Our code with v1.14.0 was:
With v2.0.1 this resulted in the following error:
hasBgpOverride is not expected here, it's read only
.As this seems to be an error with the schema, we added
schema_validation_enabled = false
. This resulted in the following terraform plan:The apply then failed with following error message:
The text was updated successfully, but these errors were encountered: