Upgrade plan
- Ofir Sonsino
As discussed in SDC weekly, we'll describe in the table below, every breaking change (with an impact on existing data or data schema) starting with Guilin and future.
Migration tasks should 1) have data or schema migrated 2) validate migration was done as expected
After creating migration tasks, we'll be able to create a script that upgrades R6 schema and data to R7.
Feature\change name | Migration task name (under asdctool) | What the task does? | Relevant Jira ticket(s) |
|---|---|---|---|
More info
Migration table - SDC keeps last migration version in Cassandra and compares it on startup.
typesToUpgrade.json file - add heat types and TOSCA normative types, to have them upgraded in the catalog between releases.
Data types limitation - data types and policies currently has no versioning. Hence we can only add properties but not remove or change their type, to allow existing data consistency with previous release data types.