-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consistent Identity Blocks across the provider #15187
Comments
This functionality has been released in v3.0.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. |
Community Note
Background
In 2.x versions of the Provider, the
identity
block differs depending on the resource being used, such that the following combinations are possible:Current Behavior
No identity (by omitting the block):
No identity (by specifying 'type = None'):
System Assigned Identity:
User Assigned Identity:
System Assigned, User Assigned Identity:
While the two "No identity" blocks carry the same result, they currently aren't reconciled into Terraform correctly. Some resources require specifying the block and others omitting it, which is confusing.
New or Affected Resource(s)
Proposed Behavior
As a part of the upcoming 3.0 we'll be making these behaviorally consistent in the Provider, such that:
type = "None"
), theidentity
block should be omitted.No identity (by omitting the block):
System Assigned
,User Assigned
orSystemAssigned, UserAssigned
identity, the block must be specified as it is today.System Assigned Identity:
User Assigned Identity:
System Assigned, User Assigned Identity:
The text was updated successfully, but these errors were encountered: