• Potentially reuse/expand on existing DDR: https://docs.google.com/document/d/1EC0jS8Slie2Tql4STN-Xcv03qLHEoEZn7omHghHB0tA/edit?tab=t.0#heading=h.pfjzbznm9cbk
  – This DDR has a space for the data models that we should add during this spike

• Output is decision/design how all v2 models will look like and document it
• Create implementation tickets for v2 models like there is for v2 role
  • https://issues.redhat.com/browse/RHCLOUD-35356

 
This spike aims to define and design the V2 data models for RBAC. Starting with Roles and ending with RoleBindings. We could potentially split this ticket into smaller spikes for each of the v2 models. Take a look at the current models that exist in RBAC: 
 

• Roles 
• Groups
• Workspaces
• Permission
• Access
• Principals
• Role Bindings (does not currently exist & therefore should be the last v2 models defined) 

 
We can potentially reuse some of the existing v1 models and APIs, which might result in potentially less logic/code to write. 
 
The output of this spike will be a clear decision and design document detailing how the v2 models will look, serving as a collaborative working document for RBAC engineers. 
 
Goals of this Spike:
  * Design and define the V2 data models.

• Decide whether to reuse existing RBAC data models/APIs or create net-new models, documenting the rationale

For people reading this in the future: the primary outcome of this work was KSL-026.