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

Updating Kafka feature for Azure Eventhub Namespace fails #4239

Closed
sschne opened this issue Sep 4, 2019 · 5 comments · Fixed by #4264
Closed

Updating Kafka feature for Azure Eventhub Namespace fails #4239

sschne opened this issue Sep 4, 2019 · 5 comments · Fixed by #4264

Comments

@sschne
Copy link
Contributor

sschne commented Sep 4, 2019

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 (and AzureRM Provider) Version

Terraform v0.12.7

  • provider.azurerm v1.33.1

Affected Resource(s)

  • azurerm_eventhub_namespace

Terraform Configuration Files

resource "azurerm_eventhub_namespace" "ns" {
  name                     = var.namespace
  location                 = var.location
  resource_group_name      = var.resource_group_name
  sku                      = var.sku
  capacity                 = var.capacity
  auto_inflate_enabled     = var.auto_inflate_enabled
  maximum_throughput_units = var.maximum_throughput_units
  kafka_enabled            = var.kafka_enabled

  tags = var.tags
}

Debug Output

Panic Output

Expected Behavior

Eventhub Namespace should destroy / create as updating kafka feature is not supported.

Actual Behavior

Terraform fails with error:
Error: eventhub.NamespacesClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="BadRequest" Message="Updating the KafkaEnabled property on a namespace is not supported. CorrelationId: xxxx

Steps to Reproduce

  1. terraform apply
  2. Change kafka_enabled to either true/false
  3. terraform apply

Important Factoids

References

@nexxai
Copy link
Contributor

nexxai commented Sep 5, 2019

Submitted PR #4264

@ghost
Copy link

ghost commented Sep 18, 2019

This has been released in version 1.34.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 1.34.0"
}
# ... other configuration ...

@plaformsre
Copy link

plaformsre commented Sep 24, 2019

Just tested it via terraform with the provider version mentioned above and still returning the error message.

* azurerm_template_deployment.event_hub_kafka_enabled_firewallrule: Error waiting for deployment: Code="DeploymentFailed" Message="At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details." Details=[{"code":"BadRequest","message":"{\r\n \"error\": {\r\n \"message\": \"Updating the KafkaEnabled property on a namespace is not supported. CorrelationId: ***\",\r\n \"code\": \"BadRequest\"\r\n }\r\n}"}]

@tombuildsstuff
Copy link
Contributor

@mapdegree unfortunately that's not supported using an ARM Template Deployment - this fix applies to the Terraform resource azurerm_eventhub_namespace.

@ghost
Copy link

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

@ghost ghost locked and limited conversation to collaborators Oct 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants