← Back to parent Epic
MAZENG-FT-9 · Curate saved cloud-account connections
Why it matters
Saved cloud connections become misleading or unsafe when their labels and lifecycle cannot be maintained.
Expected outcome
Keeps reusable cloud-account choices understandable and under the user's control.
In scope
- List cloud-account connections owned by the signed-in user.
- Edit a saved connection's name and description.
- Confirm and remove an obsolete saved connection.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic (product lead)
- Solution approval
- PENDING
Acceptance
Acceptance outcomes
- 01
Only connections available to the signed-in user appear.
- 02
Edited name and description persist after reload.
- 03
Removal requires confirmation and removes the connection from future selections.
- 04
A user cannot update or remove another user's connection by supplying its identifier.
Dependencies and risks
Dependencies
None recorded.
Risks
- Legacy update and delete endpoints accept only a connection identifier and do not visibly enforce ownership; that authorization defect must not be carried forward.
- Removal semantics for projects that reference a connection require an explicit dependency and user-feedback decision.
Authoritative Architecture tasks
No authoritative Architecture tasks are linked.