-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Comments
what about the possibility to link an iot hub to the newly created dps? that would be great. |
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. |
Hey @ezhaar and @ukphillips, #3922 should finish up this issue by adding support for linked hubs |
@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 |
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! |
Community Note
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.
New or Affected Resource(s)
This would be a new resource. Something like:
OR
Potential Terraform Configuration
An extended version of this would include the options for access-policy, certificate, and linked-hub. That might look something like:
References
The text was updated successfully, but these errors were encountered: