Improvement: automatically generate UUID for azurerm_role_assignment

[jansepke]

Terraform Version

Terraform v0.11.1

• provider.azurerm v1.0.0

Affected Resource(s)

azurerm_role_assignment

Terraform Configuration Files

resource "azurerm_role_assignment" "test" {
  name               = "1a679e7d-719c-42bf-9141-15c8de83836d" // random UUID
  scope              = "..."
  role_definition_id = "..."
  principal_id       = "..."
}

Hi there,

I don't understand why I need to specify a unique UUID for a azurerm_role_assignment resource. This makes this piece of code less modular. Would it be possible to make this property optional and fall back to an automatically generated UUID? Or is there any way to generate a static UUID in terraform? When I use the ${uuid()} interpolation, terraform will recreate the azurerm_role_assignment each run because the interpolation has changed.

[tombuildsstuff]

hey @jansepke

Thanks for opening this issue, I've added support for this in #685 which has been merged and will be released as part of v1.0.2 of the AzureRM Provider.

Thanks!

[JamesDLD]

Thanks for this improvement, just raised the same improvement here #1371 for the resource azurerm_role_definition

[ghost]

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!