terraform-provider-azurerm: Event Hub Authorization Rule is not working as expected.

Is there an existing issue for this?

  • I have searched the existing issues

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

Terraform Version

0.13.0

AzureRM Provider Version

2.58.0

Affected Resource(s)/Data Source(s)

azurerm_eventhub_authorization_rule

Terraform Configuration Files

resource "azurerm_eventhub_authorization_rule" "jira_notifications_consumer" {
  name                = "consumer"
  namespace_name      = azurerm_eventhub_namespace.jiranotifications.name
  eventhub_name       = core-shs-eun1
  resource_group_name = azurerm_resource_group.eventhub.name
  listen              = true
  send                = false
  manage              = false
}

Debug Output/Panic Output

Error making Read request on Azure EventHub Authorization Rule List Keys : eventhub.EventHubsClient#ListKeys: Failure responding to request: StatusCode=405 -- Original Error: autorest/azure: Service returned an error. Status=405 Code="" Message="The requested resource does not support http method 'POST'."

Expected Behaviour

Creation of authorization Rule

Actual Behaviour

Gives an error: Error: Error making Read request on Azure EventHub Authorization Rule List Keys : eventhub.EventHubsClient#ListKeys: Failure responding to request: StatusCode=405 – Original Error: autorest/azure: Service returned an error. Status=405 Code=“” Message=“The requested resource does not support http method ‘POST’.”

Steps to Reproduce

terraform apply.

Important Factoids

No response

References

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 6
  • Comments: 19 (6 by maintainers)

Most upvoted comments

@sathishkumar3009 I’m working on it, will update soon

@xiaxyi - I applied it with the version 3.14.0 and it works without an error.

Thank you so much for your support.

@sathishkumar3009 I see, the cause is the ID in the state is composed of the elements in lower case… Let me check how to work it out.

Thanks I will check and update.