orchestrator-core icon indicating copy to clipboard operation
orchestrator-core copied to clipboard

[Feature]: Add Resource Type Deprecation to Migration Generator

Open crankynetman opened this issue 2 years ago • 1 comments

Contact Details

[email protected]

What should we build?

Today, if you delete a resource type (as it is no longer used, for example) you would write a migration to delete that resource type. We should add support for this to the migration generator (maybe it's already there) but also add support to the orch core for going through all resource types that have been deleted and remove them from the database on any subscription instance that is in the TERMINATED state.

Relevant pseudo code

No response

crankynetman avatar Mar 05 '24 12:03 crankynetman

Check if cascading deletes work, and document behaviour.

hanstrompert avatar Mar 03 '25 09:03 hanstrompert

The migration generator already has support for deleting removed resource types. This is also documented: https://workfloworchestrator.org/orchestrator-core/reference-docs/cli/#migrate-domain-models

The best solution would be to version all domain models and workflows so it is clear which resource types are obsolete (only used by older versions) and which are not. Just removing resource types and values from terminated subscriptions that are not used by not terminated subscriptions is a decision that needs to be made by each orchestrator implementor himself.

hanstrompert avatar Jul 07 '25 11:07 hanstrompert