Update All services with one click

[odeimaiz]

What do these changes do?

Related issue/s

closes ITISFoundation/osparc-issues#572

How to test

Checklist

[codecov]

Codecov Report

Merging #2721 (1e26daf) into master (5903c51) will increase coverage by 0.1%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           master   #2721     +/-   ##
========================================
+ Coverage    78.0%   78.1%   +0.1%     
========================================
  Files         643     643             
  Lines       26391   26391             
  Branches     2555    2555             
========================================
+ Hits        20585   20621     +36     
+ Misses       5108    5081     -27     
+ Partials      698     689      -9     

Flag	Coverage Δ
integrationtests	67.0% <ø> (-0.1%)	⬇️
unittests	73.8% <ø> (+0.1%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...rvice-library/src/servicelib/common_aiopg_utils.py	88.2% <0.0%> (-8.9%)	⬇️
..._director_v2/modules/dynamic_sidecar/client_api.py	68.7% <0.0%> (-1.9%)	⬇️
...tor_v2/modules/dynamic_sidecar/scheduler/events.py	93.6% <0.0%> (-1.5%)	⬇️
...ector_v2/modules/dynamic_sidecar/scheduler/task.py	85.9% <0.0%> (-0.6%)	⬇️
..._director_v2/modules/dynamic_sidecar/docker_api.py	87.2% <0.0%> (+0.5%)	⬆️
...simcore_service_webserver/projects/projects_api.py	88.4% <0.0%> (+0.7%)	⬆️
...car/src/simcore_service_dask_sidecar/dask_utils.py	91.7% <0.0%> (+1.0%)	⬆️
.../simcore_service_webserver/projects/projects_db.py	90.7% <0.0%> (+1.1%)	⬆️
...mcore_service_webserver/projects/projects_utils.py	80.5% <0.0%> (+4.2%)	⬆️
...re_service_webserver/projects/projects_handlers.py	83.3% <0.0%> (+12.1%)	⬆️

[sanderegg]

love it! thanks for the present!!

[pcrespov]

Great!

THOUGHT: Still updates the latest patch, right?

From https://semver.org/

Given a version number MAJOR.MINOR.PATCH, increment the:

1. MAJOR version when you make incompatible API changes,
2. MINOR version when you add functionality in a backwards compatible manner, and
3. PATCH version when you make backwards compatible bug fixes.

Should we add an option to select what sort of upgrade as well? At least for MINOR?

[odeimaiz]

Great!

THOUGHT: Still updates the latest patch, right?

From https://semver.org/

Given a version number MAJOR.MINOR.PATCH, increment the:

1. MAJOR version when you make incompatible API changes,
2. MINOR version when you add functionality in a backwards compatible manner, and
3. PATCH version when you make backwards compatible bug fixes.

Should we add an option to select what sort of upgrade as well? At least for MINOR?

Correct, for now, it only applies to Patches.

A Minor upgrade in the service might involve updates in the ports (new port, updates on units....) and this would break connections. I'm not sure you want to go that far.

[pcrespov]

A Minor upgrade in the service might involve updates in the ports (new port, updates on units....) and this would break connections. I'm not sure you want to go that far.

@odeimaiz a minor upgrade should be backwards compatible ( read definitions above) -> no interface change expected! We could eventually enforce that in the service library test when we evaluate services