Users need deterministic Terraform files that correspond to an identified visual-design revision and its selected resources.
Why it matters
Users need deterministic Terraform files that correspond to an identified visual-design revision and its selected resources.
Expected outcome
Users can review a complete per-account Terraform bundle before using it in any infrastructure workflow.
In scope
- Generate resource, provider, required-provider and version, and variable files for each cloud account.
- Bind generated names, values, relationships, provider, and region to one identified design revision.
- Fail visibly for invalid or unsupported design structures rather than presenting a partial bundle as valid.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic (product lead)
- Parent Epic
- MAZENG-EP-7
- Solution approval
- PENDING