Simplify history model for SC deployments away from "lifecycle" concept. This is to support the simple deployment history UI coming up.
Add a new table and populate it with existing lifecycle data.
Keep old tables around for the time being (no size worries) and delete later.
Change all the code to refer to the new deployment history table and API references to those fields.
Tested out everything here to ensure that promotions + status, and audits (on admin side) all still work for all cases. As the lifecycle history was used to determine current allowed promotions and such.
Types of changes
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
[x] I have checked that unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
Further comments
Key for this PR is to keep all GETOK structure the same as it always was, no additional changes other than replacing reads and writes with the new table instead of lifecycle ones.
Description
SHOWCASE-781
Simplify history model for SC deployments away from "lifecycle" concept. This is to support the simple deployment history UI coming up.
Add a new table and populate it with existing lifecycle data. Keep old tables around for the time being (no size worries) and delete later. Change all the code to refer to the new deployment history table and API references to those fields.
Tested out everything here to ensure that promotions + status, and audits (on admin side) all still work for all cases. As the lifecycle history was used to determine current allowed promotions and such.
Types of changes
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Checklist
Further comments
Key for this PR is to keep all GETOK structure the same as it always was, no additional changes other than replacing reads and writes with the new table instead of lifecycle ones.
Model of new table: