IotOperation resource availability #30915
Open
+25,797
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Community Note
Description
This addition introduces comprehensive support for Azure IoT Operations, Microsoft's unified industrial IoT platform, to the AzureRM Terraform provider. The implementation includes a complete suite of resources that enable users to deploy and manage edge-to-cloud IoT solutions through Infrastructure as Code. The core foundation begins with the azurerm_iotoperations_instance resource, which serves as the container for all IoT Operations components and requires deployment to Arc-enabled Kubernetes environments via custom locations. Built upon this foundation is the azurerm_iotoperations_broker resource, providing a scalable MQTT message broker with configurable cardinality for both backend (partitions, redundancy, workers) and frontend (replicas, workers) components. Network connectivity is handled through azurerm_iotoperations_broker_listener resources, which support multiple protocols (MQTT, WebSockets, HTTP) with enterprise-grade security features including TLS encryption, cert-manager integration for automated certificate lifecycle management, and configurable authentication and authorization policies. The platform's data processing capabilities are enabled through azurerm_iotoperations_dataflow resources that define transformation and routing workflows, supported by azurerm_iotoperations_dataflow_profile resources for performance tuning and azurerm_iotoperations_dataflow_endpoint resources for connecting to external systems like Azure Data Explorer, Storage accounts, and Event Hubs. Security and access control are managed through dedicated azurerm_iotoperations_broker_authentication and azurerm_iotoperations_broker_authorization resources, providing fine-grained control over device and application access to the MQTT broker. This comprehensive resource set enables organizations to implement complete industrial IoT scenarios with edge computing capabilities, real-time data processing, secure device communication, and seamless integration with Azure cloud services, all managed declaratively through Terraform's infrastructure-as-code approach.
PR Checklist
For example: “
resource_name_here
- description of change e.g. adding propertynew_property_name_here
”Changes to existing Resource / Data Source
Testing
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_resource
- support for thething1
property [GH-00000]This is a (please select all that apply):
Related Issue(s)
Fixes #0000
AI Assistance Disclosure
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the provider.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
Note
If this PR changes meaningfully during the course of review please update the title and description as required.