-
Task
-
Resolution: Unresolved
-
Major
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
None
-
Unset
-
None
-
-
-
5
-
Access & Management Sprint 116, Access & Management Sprint 117, Access & Management Sprint 118
In order to ensure that V1 APIs can be used in a V2 world, the V1 models, the V2 models, and Inventory must be in sync. Implementing this requires both updating the dual-write code (which currently keeps the V1 models and Inventory in sync) to also update RBAC's local V2 models.
This ticket is for ensuring that all updates made through the API update the appropriate V2 models. In contrast, RHCLOUD-35354 is for updating the one-time migration code.
This is not a Spike because the unknowns about how to do this should be resolved by RHCLOUD-41952.
The V2 models PoC PR may be useful as a starting point for this work (but note that the design of the models has since changed slightly; see the DDR for details).
- depends on
-
RHCLOUD-35356 Create V2 role model
-
- Closed
-
-
-
- Closed
-
-
RHCLOUD-41952 [SPIKE] Migrating existing V1 data to V2 models
-
- Code Review
-
- relates to
-
-
- In Progress
-