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 Device Provisioning Resource #1712

Closed
jgardner04 opened this issue Aug 2, 2018 · 5 comments · Fixed by #3922
Closed

IoT Device Provisioning Resource #1712

jgardner04 opened this issue Aug 2, 2018 · 5 comments · Fixed by #3922

Comments

@jgardner04
Copy link
Contributor

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

Description

Add a resource for Azure IoT Device Provisioning Service. This would likely be a new resource; something like azurerm_iotdps. This command would be completed through the Azure-CLI through a command like that below.

az iot dps create --name MyDps --resource-group MyResourceGroup --location westus

New or Affected Resource(s)

This would be a new resource. Something like:

  • azurerm_iotdps
    OR
  • azurerm_iot_dps

Potential Terraform Configuration

resource "azurerm_iot_dps" "test" {
  name                             = "test"
  resource_group_name  = "test"
  location                         = "West US"
  sku                                = "S1"

  tags {
    "purpose" = "testing"
  }
}

An extended version of this would include the options for access-policy, certificate, and linked-hub. That might look something like:

resource "azurerm_iot_dps" "test" {
  name                             = "test"
  resource_group_name  = "test"
  location                         = "West US"
  sku                                = "S1"
  access_policy {
    name = "test_policy"
    rights = "DeviceConnect"
    shared_access_policy {
      primary_key = "123"
      secondary_key = "abc"
    }
  }
  certificate {
    contents = "${base64encode(file("certificate-to-import.pfx"))}"
    password = "Pass@word1"
  }
  linked-hub = "${azurerm_iothub.test.name}"

  tags {
    "purpose" = "testing"
  }
}

References

@ezhaar
Copy link

ezhaar commented Jul 2, 2019

what about the possibility to link an iot hub to the newly created dps? that would be great.

@ukphillips
Copy link

Agreed we need the IoT hub linkage to make this useful - Glad to see this started but without the hubs it does not add a lot of value.

@mbfrahry
Copy link
Member

Hey @ezhaar and @ukphillips, #3922 should finish up this issue by adding support for linked hubs

@ezhaar
Copy link

ezhaar commented Jul 28, 2019

@mbfrahry I found another issue with the DPS resource. I filed a bug report in the TF repo. Perhaps I should file it here instead? hashicorp/terraform#22228

@ghost
Copy link

ghost commented Sep 1, 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 Sep 1, 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.

5 participants