provide backward compatibility or awareness when upgrading Fed-BioMed
As a Fed-BioMed "user" I want the software to deal with pre-existing installation of older Fed-BioMed software versions, when re-installing/upgrading Fed-BioMed.
Note: In this case "user" might be:
- end user when doing
dev
installation on a laptop - IT support team when doing a real deployement (with
vpn
installation mode) - ...
Context: currently Fed-BioMed assumes it is installed from scratch and coherently. This might not always be the case for example:
- a pre-existing version of Fed-BioMed is upgraded but configuration files, breakpoints, etc. from previous installation are re-used
- node and researcher are installed with different versions
We need to add:
- awareness of version for the following components:
- configuration files
- breakpoints content
- node-researcher messaging protocol
- other ?
The version might be a Fed-BioMed version (eg: for Fed-BioMed v4.3) or for the component (eg: configuration file version 6).
- optionally backward compatibility. Then need to decide a policy, and a function/module assessing the compatibility between two versions.
Dear user, please keep the lign below when submitting an issue:
Edited by VESIN Marc