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

data.azurerm_azuread_group #2326

Closed
lawrenae opened this issue Nov 15, 2018 · 2 comments
Closed

data.azurerm_azuread_group #2326

lawrenae opened this issue Nov 15, 2018 · 2 comments

Comments

@lawrenae
Copy link
Contributor

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

My Basic desire is to not have to figure out the objectID of a group by hand before assigning roles to it in terraform.

Today, I have to do something like this:

az ad group show --group my_cool_group

in order to retrieve the objectId, then hard code that id into a locals block in terraform and then refer to it in azurerm_role_assignment

Based on my reading of the API and the go client, this looks doable, but am not sure what roles/permissions are required yet

New or Affected Data Source(s)

  • azurerm_azuread_group

Potential Terraform Configuration

data "azurerm_azuread_group" "test" {
     display_name = "my_cool_group"
}

resource "azurerm_role_assignment" "azure_cloud_support_as_owner_owner" {
  scope                = "${azurerm_resource_group.current.id}"
  role_definition_name = "Owner"
  principal_id         = "${data.azurerm_azuread_group.test.id}"
}

References

@tombuildsstuff
Copy link
Contributor

hi @lawrenae

Thanks for opening this issue :)

Support for a Data Source for Groups has previously been requested in #1272 which, rather than having multiple issues tracking the same thing I'm going to close this issue in favour of - please subscribe to that issue for updates. We've recently opened a proposal to move the Azure Active Directory resources out into their own Provider - which is being tracked in #2322 which may also be worth subscribing too.

Thanks!

@ghost
Copy link

ghost commented Mar 5, 2019

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants