azurerm_linux_function_app Storage options not working

[rdvansloten]

Is there an existing issue for this?

• I have searched the existing issues

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 Version

1.2.0

AzureRM Provider Version

3.29.1

Affected Resource(s)/Data Source(s)

azurerm_linux_function_app

Terraform Configuration Files

resource "azurerm_linux_function_app" "function_apps" {
  name                          = "myapp"
  resource_group_name           = azurerm_resource_group.main.name
  location                      = var.location
  storage_account_name          = azurerm_storage_account.function_app_storage.name
  storage_account_access_key    = azurerm_storage_account.function_app_storage.primary_access_key
  service_plan_id               = azurerm_service_plan.asp.id
  https_only                    = true

  identity {
    type         = "UserAssigned"
    identity_ids = [azurerm_user_assigned_identity.function_apps.id]
  }

  site_config {
    application_insights_connection_string = azurerm_application_insights.function_app.connection_string
    application_insights_key               = azurerm_application_insights.function_app.instrumentation_key

    application_stack {
      python_version = "3.9"
    }

    cors {
      allowed_origins = [
        "mydomain.com"
      ]
      support_credentials = true
    }
  }

  app_settings = {
    APP_PARTITION_KEY            = var.app_partition_key
    ENVIRONMENT                  = var.environment
    HOME_URL                     = var.home_url
  }
}

### Debug Output/Panic Output

```shell
-

Expected Behaviour

storage_account_name and storage_account_access_key are set, and the promised vars should have been generated. They have not.

From the docs:
"Note: For storage related settings, please use related properties that are available such as storage_account_access_key, terraform will assign the value to keys such as WEBSITE_CONTENTAZUREFILECONNECTIONSTRING, AzureWebJobsStorage in app_setting."

AzureWebJobsStorage vars are set, but WEBSITE_CONTENTAZUREFILECONNECTIONSTRING and WEBSITE_CONTENTSHARE are not.

When creating through the Portal, this all works. The docs are either wrong or incomplete, or the module is not doing what it should.

Actual Behaviour

The environment variables that were promised, are not generated. This causes deployments to fail, because there is no storage.

Steps to Reproduce

No response

Important Factoids

No response

References

No response

[xiaxyi]

Thanks @rdvansloten for raising this issue, may I know the service plan? Is it standard plan or premium/ elastic?

This setting is only required for consumption/ premium plan

https://learn.microsoft.com/en-us/azure/azure-functions/functions-app-settings#website_contentazurefileconnectionstring

[rdvansloten]

@xiaxyi I am using Consumption (Y) tier. Another thing is that if I deploy via Terraform and set these settings manually, I am unable to push Python code via VS Code. I have to create the Functions manually, then import. It seems that this env var needs to be set at create time, or the storage never gets linked.

[xiaxyi]

@rdvansloten I will raise a pr for the fix, the current provider didn't sets this property for consumption plan.

[xiaxyi]

@rdvansloten , you can track the status in the pr #18258

[github-actions]

This functionality has been released in v3.48.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.