Skip to main content

← Back to parent Epic

MAZENG-FT-57 · Terraform preflight validation, formatting, and compliance

Feature intent

Users need to detect syntax, formatting, and policy problems safely before creating or changing a Maze project.

Why it matters

Users need to detect syntax, formatting, and policy problems safely before creating or changing a Maze project.

Expected outcome

CLI users receive structured, reproducible preflight results without command or path injection risk.

In scope

  • Workspace-isolated Terraform validation, formatting, and compliance checks.
  • Structured file, rule, severity, and exit semantics.
  • Reviewable formatting diffs with explicit application and disclosed tool versions or skipped checks.
Delivery status
IN_BACKLOG
Owner
RootAtSkic (product lead)
Parent Epic
MAZENG-EP-15
Solution approval
PENDING

Acceptance

Acceptance outcomes

  1. 01

    Validate, format, and compliance operate only on the caller's isolated workspace.

  2. 02

    Results are structured by file, rule, and severity with deterministic exit semantics.

  3. 03

    Formatting returns a reviewable diff and requires explicit application.

  4. 04

    Policy tool and version plus skipped checks are disclosed.

Dependencies and risks

Dependencies

None recorded.

Risks

  • Legacy invokes mutating operations through GET endpoints with caller-controlled paths.
  • Legacy concatenates path input into a synchronous shell command, creating command-injection exposure.
  • Unsafe legacy execution behavior must not become an acceptance requirement.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

Original source