azurerm_function_app/storage_account_access_key signals changed on every run

[vanmash]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

• terraform v1.0.11
• azurerm v2.85.0

Affected Resource(s)

• azurerm_function_app

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp
resource "azurerm_function_app" "func" {
  name                       = "func-${var.PRODUCT}-${var.ENV_LONG}"
  location                   = azurerm_resource_group.rg.location
  resource_group_name        = azurerm_resource_group.rg.name
  app_service_plan_id        = azurerm_app_service_plan.asp.id
  storage_account_name       = azurerm_storage_account.st.name
  storage_account_access_key = azurerm_storage_account.st.primary_connection_string
  version                    = "~3"
  enable_builtin_logging     = true
}

Debug Output

Panic Output

Expected Behaviour

plan should detect no changes.

Actual Behaviour

Every plan shows

  # azurerm_function_app.func[0] will be updated in-place
  ~ resource "azurerm_function_app" "func" {
        id                              = "/subscriptions/***"
        name                            = "func-***-production"
      ~ storage_account_access_key      = (sensitive value)
}

Steps to Reproduce

1. terraform apply

Important Factoids

References

• 0000

[njglenuk]

Has there been an update to this?

[bijenkins]

Bump, this is happening still on azurerm provider 3.43.

[frankruszel]

Hi, any updates on this issue? I am facing this in azurerm v3.114.0