Closed chris-b-chalmers closed 5 months ago
This appears to be related to terraform provider azapi version 1.13.0, which was published 2 days ago. If I back down to version 1.12.0, there is no error.
Confirmed above.
With versions.tf to specify the older version it works
terraform { required_version = "1.8.2"
required_providers { azurerm = ">= 3.100.0" azapi = { source = "azure/azapi" version = "1.12.0" } } }
[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.
[!TIP]
- To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
- To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!
[!NOTE] This message was posted as per ITA01TF.
[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.
[!TIP]
- To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
- To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!
[!NOTE] This message was posted as per ITA01TF.
[!CAUTION] This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-terraform) immediate attention as it hasn't been responded to within 6 business days.
[!TIP]
- To avoid this rule being (re)triggered, the "Needs: Triage :mag:" and "Status: Response Overdue :triangular_flag_on_post:" labels must be removed when the issue is first responded to!
- Remove the "Needs: Immediate Attention :bangbang:" label once the issue has been responded to.
[!NOTE] This message was posted as per ITA02TF.
[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.
[!TIP]
- To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
- To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!
[!NOTE] This message was posted as per ITA01TF.
[!CAUTION] This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-terraform) immediate attention as it hasn't been responded to within 6 business days.
[!TIP]
- To avoid this rule being (re)triggered, the "Needs: Triage :mag:" and "Status: Response Overdue :triangular_flag_on_post:" labels must be removed when the issue is first responded to!
- Remove the "Needs: Immediate Attention :bangbang:" label once the issue has been responded to.
[!NOTE] This message was posted as per ITA02TF.
Sorry for the delayed update; we have temporarily removed the update argument until it becomes available in a future release. Code is working again.
This has been fixed with the removal of the update argument.
Is there an existing issue for this?
Greenfield/Brownfield provisioning
greenfield
Terraform Version
1.8.2
Module Version
0.1.1
AzureRM Provider Version
3.100.0
Affected Resource(s)/Data Source(s)
azapi_resource
Terraform Configuration Files
tfvars variables values
Debug Output/Panic Output
Expected Behaviour
Terraform plan succeeds
Actual Behaviour
Terraform plan fails
Steps to Reproduce
terraform init terraform plan
Important Factoids
No response
References
https://registry.terraform.io/providers/Azure/azapi/latest/docs/resources/azapi_resource has create, read, and delete but not an update entry
When removing "update = timeouts.value.update" (line 21) from main.containers.tf there is no error