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
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
Description
Current behaviour
Whenever files declared in the file block changes, it triggers a deletion and a new resource creation (see code snippet below). This is troublesome for deployments. Also because this provider assumes the destruction of a function takes 30s, but more often than None, the function still exists by the time when creation is requested, resulting in errors.
Furthermore the AZ CLI is able to update this resource in place.
#聽Expected behaviour
Updating files should trigger an inplace update of this resource.
Is there an existing issue for this?
Community Note
Description
Current behaviour
Whenever files declared in the
file
block changes, it triggers a deletion and a new resource creation (see code snippet below). This is troublesome for deployments. Also because this provider assumes the destruction of a function takes 30s, but more often than None, the function still exists by the time when creation is requested, resulting in errors.Furthermore the AZ CLI is able to update this resource in place.
#聽Expected behaviour
Updating files should trigger an inplace update of this resource.
New or Affected Resource(s)/Data Source(s)
azurerm_function_app_function
Potential Terraform Configuration
No response
References
No response
The text was updated successfully, but these errors were encountered: