cluster know which cluster_values are to be marked as deprecated upon update #32
Description
One of the challenges in regards to updating a galaxy/cluster in an automated way is to know which cluster_values do not exist anymore in the original source.
If we just iterate over the source, and update our galaxy we will not know which ones were not updated and should therefore be marked as deprecated.
Brainstorm for methods :
- an internal variable listing the uuids of the entries that were touched (
append()) since a certain moment. Flush it before using. Add a new function to deprecate the delta. - Add a new function to mark all as deprecated at once, and whenever we
append()we mark them as non-deprecated