IotOperation resource availability by HanaSheto27 · Pull Request #30915 · hashicorp/terraform-provider-azurerm

HanaSheto27 · 2025-10-20T21:57:21Z

Community Note

Please vote on this PR by adding a 👍 reaction to the original PR to help the community and maintainers prioritize for review
Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for PR followers and do not help prioritize for review

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

I have followed the guidelines in our Contributing Documentation.
I have checked to ensure there aren't other open Pull Requests for the same update/change.
I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.
I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.
For example: “resource_name_here - description of change e.g. adding property new_property_name_here”

Changes to existing Resource / Data Source

I have added an explanation of what my changes do and why I'd like you to include them (This may be covered by linking to an issue above, but may benefit from additional explanation).
I have written new tests for my resource or datasource changes & updated any relevant documentation.
I have successfully run tests with my changes locally. If not, please provide details on testing challenges that prevented you running the tests.
(For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.

Testing

My submission includes Test coverage as described in the Contribution Guide and the tests pass. (if this is not possible for any reason, please include details of why you did or could not add test coverage)

Change Log

Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.

azurerm_resource - support for the thing1 property [GH-00000]

This is a (please select all that apply):

Bug Fix
New Feature (ie adding a service, resource, or data source)
Enhancement
Breaking Change

Related Issue(s)

Fixes #0000

AI Assistance Disclosure

AI Assisted - This contribution was made by, or with the assistance of, AI/LLMs

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.

HanaSheto27 · 2025-10-31T08:16:58Z

Hey team, this PR follows the guideline with exception of Create and update to be separate function .The Azure SDK for this resource does not currently support PATCH or partial updates as a result, the Update method sends the full payload, just like Create. The code is structured to allow partial updates in the future if/when the SDK adds PATCH support.
This is important for Terraform's ignore_changes feature, which requires Update to only send changed fields.
For now, due to SDK limitations, all fields are sent on Update.

wuxu92

Hi Thanks for raising this PR, I left some comments, could you take a look and address them and I'll take another look.

wuxu92 · 2025-11-04T00:47:59Z

+  required_providers {
+    azurerm = {
+      source  = "hashicorp/azurerm"
+      version = "~> 3.0"


remove the version constraint here or version = "~> 4.xx"?

Suggested change

version = "~> 3.0"

wuxu92 · 2025-11-04T00:49:51Z

+}
+provider "azurerm" {
+  features {}
+  subscription_id = "d4ccd08b-0809-446d-a8b7-7af8a90109cd"


use a placeholder or variable, or just omit subscription_id field.

Suggested change

subscription_id = "d4ccd08b-0809-446d-a8b7-7af8a90109cd"

also applies to all other examples

wuxu92 · 2025-11-04T00:51:10Z

+  required_providers {
+    azurerm = {
+      source  = "hashicorp/azurerm"
+      version = "~> 3.0"


Suggested change

version = "~> 3.0"

also applies to all other examples

wuxu92 · 2025-11-04T00:58:07Z

+  instance_name = "REPLACE_WITH_INSTANCE_NAME"
+  broker_name   = "REPLACE_WITH_BROKER_NAME"


is there a reason we use REPLACE_WITH_XXX here? can we use a environment variable, or add a comment here about hot to setup them? the same question applies to the complete config

wuxu92 · 2025-11-04T01:06:53Z

+	ExtendedLocationName *string                   `tfschema:"extended_location_name"`
+	ExtendedLocationType *string                   `tfschema:"extended_location_type"`
+	ServiceName          *string                   `tfschema:"service_name"`
+	ServiceType          *string                   `tfschema:"service_type"`
+	Ports                []BrokerListenerPortModel `tfschema:"ports"`
+	ProvisioningState    *string                   `tfschema:"provisioning_state"`


The resource model does not use pointer types; it exclusively utilizes literal types. this also applies to all other resource model definitions.

Looked and tested the pointer issues reviewing the SDK, most of the optional parameters from the API request are pointers.

The structs defined here is for the Terraform resource, the guideline for these structs are not pointers. so we'd change it to non-pointer type to align with the provider.

wuxu92 · 2025-11-04T01:11:43Z

@@ -62,6 +62,7 @@ Healthcare
 Hybrid Compute
 IoT Central
 IoT Hub
+IoT Operations


it seems all the documents for resources are missing, could you please add documents for them

wuxu92

could you also run the Acc Tests and share the result in the PR?

wuxu92 · 2025-12-07T23:59:59Z

+	"github.com/hashicorp/go-azure-sdk/resource-manager/iotoperations/2024-11-01/dataflow"
+	"github.com/hashicorp/go-azure-sdk/resource-manager/iotoperations/2024-11-01/dataflowendpoint"
+	"github.com/hashicorp/go-azure-sdk/resource-manager/iotoperations/2024-11-01/dataflowprofile"
+	"github.com/hashicorp/go-azure-sdk/resource-manager/iotoperations/2024-11-01/instance"


the latest stable API version is 2025-10-01, can you please upgrade to the latest API version?

sreallymatt · 2026-04-09T21:50:50Z

closing due to lack of response

HanaSheto27 added 6 commits October 6, 2025 13:53

adding all resources of iottogether for terraform

9bc03f4

updating instance to follow harshicorp guideline

2602a7e

update of resources to follow PR guideline

c0ebd06

reviewed terraform PR ready

fa008f6

Save current work before merge

27e625d

updated to view all registerations

526837d

HanaSheto27 requested review from a team, WodansSon and magodo as code owners October 20, 2025 21:57

github-actions Bot added documentation dependencies size/XL labels Oct 20, 2025

following update sdk mitigaing solution

7defc83

github-actions Bot added the ai-assisted label Oct 31, 2025

wuxu92 reviewed Nov 4, 2025

View reviewed changes

update the terraform from the comment

d3195fe

wuxu92 reviewed Dec 8, 2025

View reviewed changes

rcskosir added the enhancement label Mar 25, 2026

sreallymatt added the waiting-response label Apr 1, 2026

sreallymatt closed this Apr 9, 2026

		instance_name = "REPLACE_WITH_INSTANCE_NAME"
		broker_name = "REPLACE_WITH_BROKER_NAME"

Conversation

HanaSheto27 commented Oct 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Community Note

Description

PR Checklist

Changes to existing Resource / Data Source

Testing

Change Log

Related Issue(s)

AI Assistance Disclosure

Rollback Plan

Changes to Security Controls

Uh oh!

HanaSheto27 commented Oct 31, 2025

Uh oh!

wuxu92 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

wuxu92 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

sreallymatt commented Apr 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

HanaSheto27 commented Oct 20, 2025 •

edited

Loading