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
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
I have a requirement for an azurerm_data_factory data source so that I can access the resource ID without having to create/import the resource.
Most of our developers will not have access to modify IAM roles. As a result, we are creating two Terraform configurations. The first to create the resources and the second to configure permissions. In order to apply the azurerm_role_assignment, the ID of data factory is needed.
This should also likely expose the managed identity as the resource does to avoid (confusing) use of the service principal resource for a managed identity.
The above is an example of the permissions setup required for a shared integration runtime where one data factory is given contributor access on the other.
The text was updated successfully, but these errors were encountered:
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
locked and limited conversation to collaborators
Mar 29, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
I have a requirement for an
azurerm_data_factory
data source so that I can access the resource ID without having to create/import the resource.Most of our developers will not have access to modify IAM roles. As a result, we are creating two Terraform configurations. The first to create the resources and the second to configure permissions. In order to apply the
azurerm_role_assignment
, the ID of data factory is needed.This should also likely expose the managed identity as the resource does to avoid (confusing) use of the service principal resource for a managed identity.
New or Affected Resource(s)
Potential Terraform Configuration
The above is an example of the permissions setup required for a shared integration runtime where one data factory is given contributor access on the other.
The text was updated successfully, but these errors were encountered: