Aligh swh backends for migration tools to work
Recent migration from the scrubber which did not comply fully with the documentation [1]
in regards to migration (through swh db upgrade cli) started some work to fix it [1].
The migration for the scrubber was fixed but broke some other modules as side-effects.
After further discussion with @douardda regarding the multiple proposed and somewhat wrong implementations, we've come to an understanding and a proper plan to fix everything.
-
Keep the current core code [2] (swh.core v2.10 with code and doc ok and aligned) -
swh-storage!888 (closed): Fix swh.storage's datastore to add the attribute current_version -
swh-indexer!419 (closed): Fix swh.indexer's storage datastore to add the attribute current version -
Drop unnecessary reverting diff [3] (again core code is actually ok providing ^) -
Drop diff [4] which is irrelevant as it does not fix (I misunderstood the code) -
swh-scheduler!307 (closed): Clean up unneeded code in scheduler -
#4305 (closed): Checks -
[1] https://docs.softwareheritage.org/devel/swh-core/db.html#implementation-of-a-swh-core-db-datastore
-
[3] !326 (closed)
-
[4] !327 (closed)
Migrated from T4305 (view on Phabricator)