Slack discussion: https://redhat-internal.slack.com/archives/C064X43CMLK/p1723124825754899

Have to determine what we should do:

Could do with feature flags/unleash on the front end? or
holding state in RBAC (add a status flag for workspace)
Currently we limit the depths of workspace to be 2. In M2 we would remove this limit for selected customers. Spike how we are going to achieve that: FE feature flags, BE support

This spike is initiated to investigate and define the technical approach for removing the current depth limit of two for workspace hierarchies. This enhancement is targeted for specific customers in the M2 release. This effort directly impacts the Workspace data model and associated APIs. 

The spike will focus on defining how to achieve this removal of limits, specifically by exploring Front-End (FE) feature flags for targeted customer enablement and necessary Back-End (BE) support to manage workspace depth limits. 

Goals of this Spike:

• Determine the comprehensive technical approach for enabling workspace hierarchy depths beyond 2 for select customers, encompassing both Front-End (feature flag implementation) and Back-End (data model and API adjustments).
• Propose a strategy for implementing and managing the "selected customers" aspect, likely leveraging feature flags, and how this will be managed and configured.
• Ensure that any proposed changes are consistent with established patterns like pagination used in v1 APIs.

Key Deliverables/Outputs:
1. Feature Flag Implementation Strategy: A plan detailing how feature flags will be used on the Front-End and potentially Back-End to enable this functionality specifically for selected customers. This includes how flags will be configured and managed. 
Updated Workspace Data Model Specification: A revised data model definition for Workspaces, explicitly accommodating unlimited hierarchical depth. This will serve as internal (developer experience) documentation for the new model.