Standard Plan strips out WEBSITE_CONTENTSHARE and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING

[Rgermonec]

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

azurerm_2.57.0
Terraform v0.12.29

Affected Resource(s)

Terraform Configuration Files

Below is the image of the terraform code, you can see that if the function is not on a consumption plan (AKA Dynamic - the old name) it strips the setting out. However these settings are needed to connect to the storage account regardless of whether it is on a standard or dynamic plan.

https://github.com/hashicorp/terraform-provider-azurerm/blob/3add6b0319d9121bb329187072ab6256fbcb69c2/azurerm/internal/services/web/function_app.go#L281

I don't feel it necessary to share the terraform configuration as we have troubleshooted the configuration and this part of the code is definitely the problem.

Expected Behaviour

The app should of deployed with the app setting and therefore the function app would of started up

Actual Behaviour

Terraform strips the app settings WEBSITE_CONTENTSHARE and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING without mentioning it in the plan, meaning our app service can not start up. We have to manually add the app settings back in for it to start up again.

Steps to Reproduce

Use a standard plan function app that needs access to a storage account. And see if it strips that setting out on a terraform deploy. (Our function app use to be on a Dynamic Plan, this potentially may be something to do with it)

• #0000

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