staged-discovery

What problem does it solve?

Staged discovery solves the problem of providers loading too much data and exhausting memory or slowing down discovery by splitting traversal into scoped phases.

Core Features & Use Cases

• Phased asset traversal: Break discovery into a root stage and subsequent scoped stages so traversal happens one scope level at a time.
• Memory optimization via cache isolation: Emit child scope assets without parent connection linkage to ensure the MQL resource cache is released when a scope closes.
• API cache reuse where it matters: Use parent connection linkage for leaf resources within a scope to avoid redundant API calls.
• Target-aware scanning control: Strip platform IDs from intermediate assets that are not part of the user’s discovery targets, while still emitting them so traversal can continue.

Quick Start

Ask the AI to add staged discovery support to your provider by introducing an OptionStagedDiscovery router in Discover(), implementing a root stage that emits child scope assets, and implementing one or more scoped stages that return leaf resources with correct connection config behavior and discovery-target platform ID filtering.