-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
UI for ROSA Lockbox
-
False
-
-
False
-
To Do
-
XCMSTRAT-544 - ROSA "Approved Access" (was Lockbox)
-
67% To Do, 0% In Progress, 33% Done
-
OCMUI Core Sprint 255, OCMUI Core Sprint 256
Today, via Microsoft, SRE access to ARO clusters is governed by a system called Lockbox, that provides a customer approval system for any actions by SRE on customer clusters. Many customers expect this kind of approval-first approach for when it is necessary that SRE takes action on a customer cluster. To meet customer expectations with ROSA, we plan to implement a similar system in Red Hat for the ROSA fleet (ROSA Classic and ROSA HCP).
This epic is for the Lockbox Details page:
- page actions?
- detail props to display?
Draft: OCM Approval API
UX Contact: juhale@redhat.com. OCMUX-78 is in 'consulting support' mode so I imagine ui dev will need to make rudimentary mockups if required.
- causes
-
OCMUI-1930 [Cluster details] "Access requests" tab wrongly shown for OSD clusters.
- Closed
- clones
-
OCMUI-1717 UI for ROSA Lockbox: List View
- Closed
- depends on
-
OCMUI-1717 UI for ROSA Lockbox: List View
- Closed
- is blocked by
-
OCMUI-1944 [OCM UI] Lockbox: access requests tab shown in cluster details of archive cluster
- Closed
-
OCMUI-1948 [OCM UI] Lockbox: Access requests details show wrong dates
- Closed
-
OCMUI-1949 [OCM UI] Lockbox: Access requests details show wrong/missing justification
- Closed
-
OCMUI-1992 [OCM UI] Lockbox: user with role AccessTransparencyApprover not permitted to approve/deny
- Closed
- is related to
-
OCMUI-1972 [ROSA lockbox] Restrict the UI actions on AR when cluster provided with access roles such as cluster editor and machine pool editor.
- Closed
- links to