[RS] fabric_operations_agent

[OrBaubergMicrosoft]

📝 Description

When managing Microsoft Fabric infrastructure as code,
I want to create/manage Operations Agent resources via Terraform,
so I can automate provisioning and maintain consistent Operations Agent configurations across environments.

🔬 Details / References

• Resource Name: fabric_operations_agent
• API documentation:
  • https://learn.microsoft.com/rest/api/fabric/operationsagent/items/create-operations-agent
  • https://learn.microsoft.com/rest/api/fabric/operationsagent/items/get-operations-agent
  • https://learn.microsoft.com/rest/api/fabric/operationsagent/items/update-operations-agent
  • https://learn.microsoft.com/rest/api/fabric/operationsagent/items/delete-operations-agent
  • https://learn.microsoft.com/rest/api/fabric/operationsagent/items/list-operations-agents
• Definition article: https://learn.microsoft.com/rest/api/fabric/articles/item-management/definitions/operations-agent-definition
• SDK Package: github.com/microsoft/fabric-sdk-go/fabric/operationsagent (faboperationsagent)
• SDK Version: v0.15.0
• Item Type Constant: fabcore.ItemTypeOperationsAgent
• Item Archetype: definition-properties
• Properties DTO:

  type Properties struct {
      State *AgentState // REQUIRED; Active or Inactive
  }

• Enum Types:
  • AgentState: Active, Inactive
  • DefinitionFormat: OperationsAgentV1
• Definition Paths:
  • Configurations.json (format: OperationsAgentV1)
• Estimated complexity/effort: moderate
• Preview: yes
• SPN Supported: no
• Related resources/data-sources:
  • fabric_workspace (required parent)
  • [DS] fabric_operations_agent — see paired data source issue

🚧 Potential Terraform Configuration

resource "fabric_operations_agent" "example" {
  display_name = "example"
  description  = "An example Operations Agent"
  workspace_id = fabric_workspace.example.id

  definition = {
    "Configurations.json" = {
      source = "${path.module}/operations_agent/Configurations.json"
    }
  }

  format = "OperationsAgentV1"
}

☑️ Acceptance Criteria

• Can create a new Operations Agent with required attributes
• Can read Operations Agent by ID
• Can update Operations Agent mutable attributes (display_name, description)
• Can delete Operations Agent
• Can import existing Operations Agent
• Properties are correctly mapped from SDK response (state)
• Definition can be managed (get/update) via the definition attribute
• Format OperationsAgentV1 is supported for definition operations

✅ Definition of Done

• Data Transfer Objects (DTOs)
• Resource Implementation
• Resource Added to Provider
• Unit Tests for Happy path
• Unit Tests for Error path
• Acceptance Tests
• Example in the ./examples folder
• Schema documentation in code
• Updated auto-generated provider docs with task docs