← Back to parent Epic
MAZENG-FT-44 · Publish a Maze design back to Prism through Git
Why it matters
A Prism user needs updated Maze designs returned as Prism-compatible files through a traceable Git change.
Expected outcome
Deterministic conversion and complete Git publication provide reviewable Prism files without reporting success for partial output.
In scope
- Convert supported resources, dependencies, metadata, connections, and required Terraform files.
- Write files under deterministic hyperscaler, project, and account paths.
- Reuse the task branch for repeat publication and create a pull request on first publication only after all operations succeed.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic
- Solution approval
- PENDING
Acceptance
Acceptance outcomes
- 01
Maze converts supported resources, dependencies, metadata, and connections into Prism YAML and required Terraform files.
- 02
Generated files are placed under deterministic hyperscaler/project/account paths.
- 03
Repeated publication for the same Prism task updates its existing Maze_Publish_<task> branch.
- 04
First publication creates a pull request to the target repository’s default branch.
- 05
The UI reports success only after every file, commit, branch update, and pull request operation succeeds.
Dependencies and risks
Dependencies
None recorded.
Risks
- Publication depends on Git capabilities, target-repository permissions, and a versioned Prism format.
- Legacy behavior accepts only github.ibm.com URLs and reads a server-wide Prism GitHub token.
- Legacy asynchronous traversal can generate an incomplete file set.
- Legacy code computes but omits per-resource Terraform files and incorrectly treats every non-AWS provider as Azure.
Authoritative Architecture tasks
No authoritative Architecture tasks are linked.