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
We're currently working through making the identity block behaviourally consistent across the Provider (see #15187 for details) - as a part of this we're moving to be behaviourally consistent in requiring that the identity block is specified when a Managed Identity is assigned to a resource, so that users can be sure an identity is present.
As such in order to be behaviourally consistent across the provider, unfortunately we have no plans to make this field optional & defaulted - as this would mean a breaking change to the configuration should other Identity types (such as SystemAssigned, or SystemAssigned, UserAssigned) become available in the future.
The other issue here (the identity block not being set into the state) is a regression which has been previously opened in #15411 and has been fixed by #15412 which will ship in the next release.
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.
Community Note
Terraform (and AzureRM Provider) Version
Terraform Configuration Files
N/A - Issue is rather straight forward.
Description / Feedback
Default the Identity type to "UserAssigned" as it's currently the only type available.
Edit: Also since upgrading, I'm now constantly seeing the Application Gateway doing an in-place upgrade for the Identity block.
The text was updated successfully, but these errors were encountered: