Delete or deprecate objects

[brandomr]

Should we implement cascading deletes? This will get tricky--maybe instead we should have some kind of deprecation flag. If we were to delete a model what would we do?.....

1. delete associated configs
2. remove it from projects
3. remove it from provenance (would this break chains...?)

This seems to me to be tricky but ultimately will be important to sort out.

[brandomr]

@YohannParis @pascaleproulx any thoughts on what should happen when someone deletes something? Do we even care to allow deletion right now? Removing objects from the workflow doesn't actually delete them under the hood. Removing them from the project doesn't delete them under the hood either.

A potential issue would be when the user deletes a model--delete associated simulation runs, model configs, and remove them from all projects and workflows?

[YohannParis]

I think we should keep the soft-delete that is in place right now.
I do believe it is a transition problem.