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

Support RBAC data role assignments for storage entities #2482

Closed
perbergland opened this issue Dec 10, 2018 · 2 comments
Closed

Support RBAC data role assignments for storage entities #2482

perbergland opened this issue Dec 10, 2018 · 2 comments

Comments

@perbergland
Copy link

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

RBAC support for storage will be out of preview soon so it should be supported in terraform similar to how other RBAC role assignments work.

New or Affected Resource(s)

  • azurerm_storage_container
  • azurerm_storage_account

References

https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-rbac

@tombuildsstuff
Copy link
Contributor

hi @perbergland

Thanks for opening this issue - apologies for the delayed response here!

Taking a look into this I believe this functionality should be available via the azurerm_role_assignment resource which allows for any Azure Role (built-in or custom) to be assigned to a specific scope (in this case the Storage Container) - would you be able to take a look and see if that works for you?

Since this is a question regarding Terraform Configuration rather than a bug in Terraform I'm going to close this issue for the moment; however please let us know if that doesn't work for you and we'll take another look :)

Thanks!

@ghost
Copy link

ghost commented Aug 15, 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 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Aug 15, 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

3 participants