Skip to main content

← Back to parent Epic

MAZENG-FT-19 · Configure resource intent

Feature intent

Users need to describe resource intent and change supported provider-template settings without editing implementation files directly.

Why it matters

Users need to describe resource intent and change supported provider-template settings without editing implementation files directly.

Expected outcome

Users can maintain meaningful names, notes, and supported settings while keeping the visual and persisted resource models consistent.

In scope

  • Display template-supported fields together with the resource's current name, notes, and settings.
  • Allow valid edits to resource names, notes, and provider-template-backed settings.
  • Persist configuration and visual-model changes together, with visible failure feedback.
Delivery status
IN_DESIGN
Owner
RootAtSkic (product lead)
Parent Epic
MAZENG-EP-5
Solution approval
APPROVED

Acceptance

Acceptance outcomes

  1. 01

    Selecting a resource shows the fields supported by its template and its current name, notes, and settings.

  2. 02

    Valid changes update the visual model and persisted resource representation together.

  3. 03

    Validation or persistence failure leaves the previous saved configuration intact and provides a visible error.

Dependencies and risks

Dependencies

None recorded.

Risks

  • Template drift can expose unsupported fields or omit required provider settings.
  • Non-atomic updates can leave canvas metadata and persisted resource configuration inconsistent.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

Original source