-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
RBAC Post-Migration validation and enhancements
-
False
-
-
False
-
-
Unset
-
To Do
-
100% To Do, 0% In Progress, 0% 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
Ensure the stability and completeness of the RBAC implementation by validating data parity, verifying access functionality across APIs, enhancing transaction isolation levels to serializable isolation level, and building tools to allow queries for relations api in production in read-only to support troubleshooting.
Acceptance Criteria
- Data parity between RBAC and Relation API is validated.
- Tools to continuous access checks are running as background job and logs discrepancies in monitoring tools.
- Tools to support troubleshooting of access.
- Serializable isolation level is used in RBAC.
- Tool to check existing relations in Relation API exists and is ready to use.