IoT hub endpoint created assuming same resource group

[ukphillips]

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.11.13

• provider.azurerm v1.23.0

Affected Resource(s)

IoT Hub

• azurerm_iothub

Terraform Configuration Files

resource "azurerm_iothub" "module" {
  name                = "${var.hubname}-iothub"
  resource_group_name = "${var.resource_group_name}"
  location            = "${var.location}"

  sku {
    name     = "${var.iothub_sku_name}"
    tier     = "${var.iothub_sku_tier}"
    capacity = "${var.iothub_sku_capacity}"
  }

  endpoint {
    type              = "AzureIotHub.ServiceBusQueue"
    connection_string = "${var.sb-queue-endpoint-connection-string}"
    name              = "myevent-queue"
  }

  route {
    name           = "myevent"
    source         = "DeviceMessages"
    condition      = "$body.eventType = 'myevent'"
    endpoint_names = ["myevent-queue"]
    enabled        = true
  }
}

Created successfully

Panic Output

N/A

Expected Behavior

Custom endpoint should be created on IoT hub

Actual Behavior

Custom endpoint appears created, but when you drill into it, there is a not found message. Upon drilling into the resources in the resource explorer:

My test12 queue was manually created in the portal, and is correct, but the one above it (created by TF) is created with the assumption that the servicebus will reside in the same resource group as the parent (which is the IoT hub), this is not correct and is failing to connect the resourced together properly.

I would expect there to be an optional override to specify a different resourcegrouo/subscriptionid for the queue. This also seems to be an issue with other endpoint resources as well.

Steps to Reproduce

1. Create a servicebus queue
2. Reference sb queue in an IoT endpoint

Important Factoids

N/A

References

• 0000

[neil-yechenwei]

Thanks for opening this issue. Seems currently terraform would use the resource group where iothub exists as the resource group of endpoint by default. So I made a fix to allow to specify the endpoint resource group. Hopes it would be helpful. Thanks.

[ghost]

This has been released in version 2.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 = "~> 2.34.0"
}
# ... other configuration ...

[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!