-
Spike
-
Resolution: Unresolved
-
Normal
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
None
-
Unset
-
None
-
-
-
Access & Management Sprint 115, Access & Management Sprint 116, Access & Management Sprint 117, Access & Management Sprint 118
Determine a process for migrating all existing RBAC V1 data into the newly-created V2 models so that the V2 API can be implemented.
Although actually doing the migration will involve updating the existing migration code in RBAC, actually making those changes is outside the scope of this issue (see RHCLOUD-35354 for that). The V2 models PoC PR may be useful as a reference (but note that the design of the models has since changed slightly; see the DDR for details).
Produce a document that describes the process for migrating the data in an environment. This should include the steps that are needed and take into account impacts on the service at large (e.g. downtime or read-only period).
- depends on
-
RHCLOUD-40823 [SPIKE] Model V2 models(RoleBinding and V2 roles)
-
- Code Review
-
- is depended on by
-
RHCLOUD-35354 Update migration code for new V2 models
-
- Backlog
-
-
RHCLOUD-40827 Ensure V2 models are updated from V1 API operations
-
- Backlog
-
- split from
-
RHCLOUD-40825 [SPIKE] Update migrator from V1 to V2 models
-
- Closed
-