You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# azurerm_windows_function_app.example will be updated in-place~ resource "azurerm_windows_function_app""example" {
id = ""
name = "fa-ea2-12345678-poc"~ storage_account_access_key = (sensitive value)
~ storage_account_name = "stea2funcstrg12345678" ->"stea2funcstrg87654321"# (22 unchanged attributes hidden)# (1 unchanged block hidden)
}
Expected Behaviour
The AzureWebJobsStorage and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING app settings are both updated with the new storage account.
Actual Behaviour
Only AzureWebJobsStorage is updated and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING retains the original value. This is a problem because the original storage account no longer exists.
@dantape Thank you for opening this issue. I agree with you that this issue is related to #21140 and believe #21212 will add the change you are looking for, so I have linked this issue to the PR.
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.
Is there an existing issue for this?
Community Note
Terraform Version
1.4.6
AzureRM Provider Version
3.61.0
Affected Resource(s)/Data Source(s)
azurerm_windows_function_app
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The AzureWebJobsStorage and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING app settings are both updated with the new storage account.
Actual Behaviour
Only AzureWebJobsStorage is updated and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING retains the original value. This is a problem because the original storage account no longer exists.
Steps to Reproduce
Important Factoids
No response
References
This could be related to:
#21140
#21212
The text was updated successfully, but these errors were encountered: