Closed vikljw closed 1 year ago
Hi @vikljw, thanks for reporting!
A Pull Request (#19228) to fix it has been submitted.
This functionality has been released in v3.31.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.33
AzureRM Provider Version
3.30.0
Affected Resource(s)/Data Source(s)
azurerm_logic_app_standard
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
It should be set to UserAssigned with the requested managed identity
Actual Behaviour
The resource provider sets it to SystemAssigned incorrectly during apply then keep flagging out for re-configuration during subsequent terraform plan and apply. Manual configuration of the user assign identity on the logic app was successful but was reverted incorrectly back to SystemAssigned in subsequent terraform apply.
Steps to Reproduce
No response
Important Factoids
No response
References
No response