`MAZENG-FT-22` · Define and run a bounded resource discovery

Feature intent

Users need to define and review an exact cloud discovery boundary before credentials are requested or a scan starts.

Why it matters

Users need to define and review an exact cloud discovery boundary before credentials are requested or a scan starts.

Expected outcome

Users can run a transparent, bounded discovery for a chosen project, provider account, region, and supported resource types and receive a durable outcome.

In scope

Choose a destination project, provider or account, region, and supported resource types.
Review the exact scan scope before credential collection or discovery execution.
Report per-resource-type progress and persist a completed or failed terminal state.
Reject unsupported scope and invalid credentials without presenting a partial import as complete.

Delivery status: IN_BACKLOG
Owner: RootAtSkic (product lead)
Parent Epic: MAZENG-EP-6
Solution approval: PENDING

Acceptance

Acceptance outcomes

01
The review step displays the exact project, provider, region, and selected resource types before credentials are requested or discovery begins.
02
Discovery reports progress per selected type and reaches a durable completed or failed state.
03
Unsupported providers, regions, resource types, or invalid credentials fail without silently creating an apparently complete import.

Dependencies and risks

Dependencies

None recorded.

Risks

Credential handling can expose secrets if discovery is implemented through command-string concatenation.
Process errors or partial provider results can leave discovery in a misleading non-terminal state.

Authoritative Architecture tasks

No authoritative Architecture tasks are linked.

MAZENG-FT-22 · Define and run a bounded resource discovery