Skip to main content

MAZENG-FT-25 · Generate reviewable Terraform files

Feature intent

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

Acceptance

Acceptance outcomes

  1. 01

    Generation produces resource, provider, required-provider/version, and variable files per account.

  2. 02

    Generated resource names, values, relationships, provider, and region correspond to one identified design revision.

  3. 03

    Invalid or unsupported design structures fail visibly rather than producing a partial bundle presented as valid.

Dependencies and risks

Dependencies

None recorded.

Risks

  • Non-deterministic ordering or naming can produce noisy or unsafe Terraform diffs.
  • Unsupported nested or array structures can yield a partial bundle that appears complete unless generation fails closed.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

Original source