As we introduce changes with our migration logic, we need to start keeping track of the history of the JSON.
For example, if app hits migration logic, and app editor decides to press "save". And there were issues with the migration logic, there is 1 no way to roll back, or 2 no way to see prior state of JSON. Number 2 will help us with debugging issues on our end in migration logic.
Description
As we introduce changes with our migration logic, we need to start keeping track of the history of the JSON.
For example, if app hits migration logic, and app editor decides to press "save". And there were issues with the migration logic, there is 1 no way to roll back, or 2 no way to see prior state of JSON. Number 2 will help us with debugging issues on our end in migration logic.
Existing
https://workshop.cfg.deloitte.com/cfg-ai-demo/SemossWeb/packages/client/dist/#/app/6c0d44ad-13bd-431f-b916-eb3172802ac1/edit
An app that possibly went through bad migration logic. Either A this was due to user making changes after migration logic or B bad migration logic
Reference
N/A
Tasks