-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
None
-
Unset
-
None
-
-
-
-
Access & Management Sprint 122
When cross account request is approved or expired, update the related logic to add/remove v2 data.
Currently, operations on cross-account requests only update the relevant BindingMapping model (and not any RoleBinding models). In order to eventually migrate to using RoleBindings only, we need to correctly keep the BindingMappings and RoleBindings in sync.
(Note that, unlike RHCLOUD-42212, this is about ensuring that existing cross-account request code updates the V2 models.)
- depends on
-
RHCLOUD-42231 Remove support for old BindingMapping users representation
-
- Closed
-
- is depended on by
-
RHCLOUD-42212 Investigate cross-account requests in V2
-
- Refinement
-
- is duplicated by
-
RHCLOUD-44355 Update RoleBinding models from V1 cross-account requests
-
- Closed
-
- relates to
-
RHCLOUD-44356 Update RoleBinding models from system role assignments
-
- Closed
-