Closed peterprumbach-telekom closed 1 year ago
@peterprumbach-telekom Thank you for opening this issue, the PR you mentioned (#18568) has merged. Therefore, I am going to mark this issue as closed. Per the PR: This functionality has been released in v3.34.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!
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.3.1
AzureRM Provider Version
0.39.0
Affected Resource(s)/Data Source(s)
azurerm_windows_web_app
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
No change should be made, as current_stack corresponds to the Web App settings.
Actual Behaviour
Terraform removes all attributes within current_stack and deletes the configuration (there is no terraform output showing the removal of the arguments). If you apply again with the same configuration, the attributes are added again.
Screenshot from the Activity Log in Azure: 1st "apply":
2nd "apply:
also, same behaviour on the metadata argument:
Steps to Reproduce
No response
Important Factoids
Azure GermanyWestCentral
References
No response