Description
📝 Description
When I am automating and managing data analytics infrastructure using Microsoft Fabric across multiple environments, I want to get details of Digital Twin Builder as code in Terraform.
To consistently and securely manage Digital Twin Builder as code in Terraform while automating and managing data analytics infrastructure using Microsoft Fabric across multiple environments.
🔬 Details / References
- Data Source Name:
fabric_digital_twin_builder
- API documentation:
- Get Digital Twin Builder: https://learn.microsoft.com/en-us/rest/api/fabric/digitaltwinbuilder/items/get-digital-twin-builder?tabs=HTTP
- Get Digital Twin Builder Definition: https://learn.microsoft.com/en-us/rest/api/fabric/digitaltwinbuilder/items/get-digital-twin-builder-definition?tabs=HTTP
- List Digital Twin Builders: https://learn.microsoft.com/en-us/rest/api/fabric/digitaltwinbuilder/items/list-digital-twin-builders?tabs=HTTP
- Estimated complexity/effort: easy
- Related resources/data-sources:
- Create Digital Twin Builder: https://learn.microsoft.com/en-us/rest/api/fabric/digitaltwinbuilder/items/create-digital-twin-builder?tabs=HTTP
- Delete Digital Twin Builder: https://learn.microsoft.com/en-us/rest/api/fabric/digitaltwinbuilder/items/delete-digital-twin-builder?tabs=HTTP
- Update Digital Twin Builder: https://learn.microsoft.com/en-us/rest/api/fabric/digitaltwinbuilder/items/update-digital-twin-builder?tabs=HTTP
- Update Digital Twin Builder Definition: https://learn.microsoft.com/en-us/rest/api/fabric/digitaltwinbuilder/items/update-digital-twin-builder-definition?tabs=HTTP
🚧 Potential Terraform Configuration / Desired Solution
Get item details by name
data "fabric_digital_twin_builder" "example_by_name" {
display_name = "example"
workspace_id = "00000000-0000-0000-0000-000000000000"
}
Get item details by id
data "fabric_digital_twin_builder" "example_by_id" {
id = "11111111-1111-1111-1111-111111111111"
workspace_id = "00000000-0000-0000-0000-000000000000"
}
Get item details with definition
Examples uses id
but display_name
can be used as well
data "fabric_digital_twin_builder" "example_definition" {
id = "11111111-1111-1111-1111-111111111111"
workspace_id = "00000000-0000-0000-0000-000000000000"
output_definition = true
}
Access the content of the definition with JSONPath expression
output "example_definition_content_jsonpath" {
value = provider::fabric::content_decode(data.fabric_digital_twin_builder.example_definition.definition["apacheairflowjob-content.json"].content)
}
Access the content of the definition as JSON object
output "example_definition_content_object" {
value = provider::fabric::content_decode(data.fabric_digital_twin_builder.example_definition.definition["apacheairflowjob-content.json"].content)
}
This is an invalid data source
Do not specify id
and display_name
in the same data source block
data "fabric_digital_twin_builder" "example" {
display_name = "example"
id = "11111111-1111-1111-1111-111111111111"
workspace_id = "00000000-0000-0000-0000-000000000000"
}
📎 Additional context
No response
☑️ Acceptance Criteria
No response
✅ Definition of Done
- Data Transfer Objects (DTOs)
- Data-Source Implementation
- Data-Source 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
🔰 Code of Conduct
- I agree to follow this project's Code of Conduct.