Skip to content
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

azurerm_container_app - Identity block should allow both system and user assigned, currently xor #21148

Closed
1 task done
jkrilov opened this issue Mar 27, 2023 · 2 comments · Fixed by #21149
Closed
1 task done

Comments

@jkrilov
Copy link
Contributor

jkrilov commented Mar 27, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • 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

Currently the provider only allows you to specify UserAssigned or SystemAssigned values for type in an identity block. Azure Container Apps support the use of both types of identities simultaneously, so the provider should allow you to specify both as well.

I believe changing the following line

"identity": commonschema.SystemOrUserAssignedIdentityOptional(),
to:

"identity": commonschema.SystemAssignedUserAssignedIdentityOptional(),

would allow this functionality

New or Affected Resource(s)/Data Source(s)

azurerm_container_app

Potential Terraform Configuration

identity { 
  type = "SystemAssigned, UserAssigned"
  identity_ids = ["..."] 
}

References

Container Apps - Create Or Update - REST API

@jtatum
Copy link

jtatum commented May 19, 2023

This looks like a dupe of #20437

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants