-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
AuthZ | Add support for workspaces in RBAC
-
False
-
-
False
-
Unset
-
To Do
-
CRCPLAN-233 - AuthZ | PRBAC v2 Customer Migration to Workspaces
-
50% To Do, 3% In Progress, 47% Done
-
-
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
Description of what we're building, the end goal and how we'll go about it.
Add support in RBAC for workspaces. We need to consider all of the requirements around workspaces & how they will affect both v1/v2:
Workspaces were explored in this POC branch: https://github.com/RedHatInsights/insights-rbac/commits/authz-arb-poc/
And they were initially added in this commit: https://github.com/RedHatInsights/insights-rbac/commit/290f9fc22fcf7c0949ad42c97d50e6f0ba6e70a8
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.
(need to refresh workspace requirements and update this epic)
- Workspaces exist in RBAC
- Workspaces exist with v1 functionality/ v2 functionality
Checklist
Checklist Item | Required | Notes or Comments |
---|---|---|
Workstream or external team dependencies? | Y | We need to make sure that when we add workspace support in RBAC that it is transferring to spiceDB as well. |
ADR Required?
|
Y | Workspaces will require an ADR |
Testing plans
|
Y | We need to add new automation for testing workspace support |
Known dependencies?
|
N |
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.