Skip to content

[Sprint 15] [Feature] Harden AppHost Mongo clear behavior #249

Description

@mpaulosky

Parent

What to build

Harden the AppHost MongoDB clear workflow for live local use. The clear action should remain usable while dependent resources are still running, prevent overlapping in-flight clear runs, and continue best-effort if one collection fails. Any collection-level failures should be surfaced as warnings in the operator-visible result while successful collections still report their deletion progress.

This slice completes the resilience contract for the local clear experience so the feature stays usable during active development without hiding partial-failure behavior.

Acceptance criteria

  • The clear action is not blocked solely because dependent resources such as the Web app are still running against local MongoDB.
  • Only one clear operation can be in flight at a time, and a second attempt receives clear operator feedback instead of overlapping destructive work.
  • If one collection fails to clear, the action continues remaining collections and returns warnings plus partial-progress results to the operator.
  • Automated coverage verifies live-clear behavior, single-run protection, and best-effort warning/reporting semantics.

Blocked by

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions