Add data source for azurerm_eventhub_namespace_authorization_rule

[alastairtree]

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

Summary

Please add a new data source for an existing event hub namespace auth rule, in addition to the existing resource that creates authorisation rule resources.

Motivation

If using event hubs for diagnostic logging then many resources will need auth rule keys to be able send logs to the hub. Event hubs are limited to 12 auth rules, so an auth rule needs to be reused across many resources diagnostic settings. When using the azurerm_monitor_diagnostic_setting we need to pass the ID of the event hub auth rule in the eventhub_authorization_rule_id argument, and there is no way to acquire the ID of the rule without creating it in the same template or string building based on the eventhub namespace datasource.

New or Affected Resource(s)

• azurerm_eventhub_namespace_authorization_rule

Potential Terraform Configuration

data "azurerm_eventhub_namespace_authorization_rule" "test" {
  name                           = "test-rule"
  namespace_name        = "eventhub-ns"
  resource_group_name = "eventhug-rg"
}

[alastairtree]

@katbyte I don't think that #4615 contains any related changes? Should this be reopened?

[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 👉 [email protected]. Thanks!

[katbyte]

@alastairtree, you are correct! Seems i commented and closed on the wrong issue. Reopened