← Back to parent Epic
MAZENG-FT-35 · Save an existing project as a private template
Why it matters
An authorized project member needs to preserve a useful cloud design for repeat use without rebuilding it.
Expected outcome
A complete private template lets an authorized team reuse a proven design while retaining its origin.
In scope
- Create a named private template from an existing project.
- Copy resource, canvas, provider, category, type, zoom, and cost data.
- Retain source-project and creator provenance and authorized membership.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic
- Solution approval
- PENDING
Acceptance
Acceptance outcomes
- 01
An authorized project member can provide a template name and description.
- 02
The template captures resource, canvas, provider, category, logical/deployment, zoom, and cost data.
- 03
The source project and creation provenance are retained.
- 04
Users receive clear success or failure feedback.
- 05
The resulting private template is visible only to its authorized members.
Dependencies and risks
Dependencies
None recorded.
Risks
- Template creation depends on consistent project, canvas, resource, and membership records.
- Legacy asynchronous member creation is not awaited and can leave visibility records incomplete.
- Legacy provider naming is inconsistent between azure_account and azurerm.
Authoritative Architecture tasks
No authoritative Architecture tasks are linked.