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

Iot Hub resource definition doesn't have device-to-cloud partitions settings #2821

Closed
darthkurak opened this issue Feb 1, 2019 · 3 comments · Fixed by #5505
Closed

Iot Hub resource definition doesn't have device-to-cloud partitions settings #2821

darthkurak opened this issue Feb 1, 2019 · 3 comments · Fixed by #5505

Comments

@darthkurak
Copy link

Hi! When creating IoT Hub resource in Azure in portal or Azure CLI we have ability to set device-to-cloud partitions. Default is 4, and we can setup this to 32. This is something that cannot be change after creation.
This is really important setting if we are talking about high throughput applications.
Unfortunately there is not equivalent in Terraform. As this setting cannot be changed later, the whole provisioning IoT hub with Terraform doesn't make sense - if we want this value different than default.
Please, add this one :)

Terraform Resource:
azurerm_iothub

Example of potential configuration:

resource "azurerm_iothub" "test" {
  name                = "test"
  resource_group_name = "${azurerm_resource_group.test.name}"
  location            = "${azurerm_resource_group.test.location}"

  sku {
    name     = "S1"
    tier     = "Standard"
    capacity = "1"
    device-to-cloud_partitions = "32"
  }
}
@msjonathan
Copy link

We are experiencing the same issue - as you can't update the partitions after creation.

@ghost
Copy link

ghost commented Jan 27, 2020

This has been released in version 1.42.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.42.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Mar 28, 2020

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!

@ghost ghost locked and limited conversation to collaborators Mar 28, 2020
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.

3 participants