Azure / terraform-azurerm-avm-res-storage-storageaccount

This Terraform module is designed to create Azure Storage Accounts and its related resources, including blob containers, queues, tables, and file shares. It also supports the creation of a storage account private endpoint which provides secure and direct connectivity to Azure Storage over a private network.
https://registry.terraform.io/modules/Azure/avm-res-storage-storageaccount
MIT License
21 stars 33 forks source link

main.containers.tf - An argument "update" is not expected here #78

Closed chris-b-chalmers closed 5 months ago

chris-b-chalmers commented 6 months ago

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

providers.tf

provider "azurerm" {
    features {}
    tenant_id       = ""
    subscription_id = ""
}

base.tf

resource "azurerm_resource_group" "example" {
    name     = "rg-storage-account-example"
    location = "UK South"
}

resource.tf

module "example" {
    source              = "git::https://github.com/Azure/terraform-azurerm-avm-res-storage-storageaccount"
    resource_group_name = azurerm_resource_group.example.name
    location            = azurerm_resource_group.example.location
    name                = "saccuksupdatebug"
}

versions.tf

terraform {
  required_version = "1.8.2"

  required_providers {
    azurerm = ">= 3.100.0"
  }
}

tfvars variables values

N/A

Debug Output/Panic Output

╷
│ Error: Unsupported argument
│ 
│   on .terraform/modules/example/main.containers.tf line 21, in resource "azapi_resource" "containers":
│   21:       update = timeouts.value.update
│ 
│ An argument named "update" is not expected here.
╵

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

JoshuaMcConnaughey commented 6 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.

chris-b-chalmers commented 6 months ago

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" } } }

microsoft-github-policy-service[bot] commented 6 months ago

[!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.

microsoft-github-policy-service[bot] commented 6 months ago

[!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.

microsoft-github-policy-service[bot] commented 6 months ago

[!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.

microsoft-github-policy-service[bot] commented 5 months ago

[!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.

microsoft-github-policy-service[bot] commented 5 months ago

[!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.

chinthakaru commented 5 months ago

Sorry for the delayed update; we have temporarily removed the update argument until it becomes available in a future release. Code is working again.

chinthakaru commented 5 months ago

This has been fixed with the removal of the update argument.