← Back to parent Epic
MAZENG-FT-43 · Import a Prism design into Maze
Why it matters
A user needs to convert an existing Prism design into an editable Maze canvas without corrupting the current project.
Expected outcome
A confirmed, atomic conversion preserves supported resources and relationships or leaves the existing project unchanged with a clear failure.
In scope
- Select a Prism path and supported provider.
- Retrieve and parse all YAML files beneath the selected path.
- Convert and atomically replace resource and canvas data only after confirmation and full validation.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic
- Solution approval
- PENDING
Acceptance
Acceptance outcomes
- 01
The user selects a Prism path and supported cloud provider.
- 02
Maze retrieves and parses all YAML files beneath that path.
- 03
Converted resource and canvas data preserve supported resources and relationships.
- 04
Import clearly warns that current canvas data will be replaced and requires confirmation.
- 05
Conversion or persistence failure leaves the existing project unchanged and identifies the failed file/path.
Dependencies and risks
Dependencies
None recorded.
Risks
- Import depends on a versioned Prism YAML contract and atomic project replacement.
- Legacy import is hard-coded to one repository path and offers only AWS and Azure.
- The legacy endpoint declares roles but omits the RolesGuard.
- Legacy replacement uses two independent writes and can leave partial state.
Authoritative Architecture tasks
No authoritative Architecture tasks are linked.