Review the CRCPLAN parent feature for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.

Summary and goal

Expected result:

In ephemeral, we should be able to do the following

Given persistence is enabled

• Report 10000 host resources (maybe more?) to v1beta2 API
• Exercise all read calls and see what breaks
• Consider using the performance lab environments if ephemeral does not work well
• Do not worry about consistency issues (i.e. Consistency between MFs internal DBs i.e RBAC, Inventory and SpiceDB), but keep the team informed.

Acceptance Criteria 

These conditions must be met for the epic to be considered complete. This provides a detailed definition of scope and the expected outcomes, written from a user's point of view.

Checklist

Open Questions

Capture any open questions and resolutions related to the epic goal or acceptance criteria. Add any additional details, questions or decisions that need to be made or addressed.