Adding image digests to databases

[GitHK]

What do these changes do?

Ensure that the current version of the DB will not change if new versions are released or overwritten remotely.

Related issue number

How to test

Checklist

• Did you change any service's API? Then make sure to bundle document and upgrade version (make openapi-specs, git commit ... and then make version-*)
• Unit tests for the changes exist
• Runs in the swarm
• Documentation reflects the changes
• New module? Add your github username to .github/CODEOWNERS

[codecov]

Codecov Report

Merging #1914 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1914   +/-   ##
======================================
  Coverage    72.7%   72.7%           
======================================
  Files         342     342           
  Lines       13019   13019           
  Branches     1383    1383           
======================================
  Hits         9474    9474           
  Misses       3162    3162           
  Partials      383     383           

Flag	Coverage Δ
#integrationtests	60.9% <ø> (+<0.1%)	⬆️
#unittests	66.0% <ø> (ø)

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

Impacted Files	Coverage Δ
...ce_webserver/resource_manager/garbage_collector.py	75.8% <0.0%> (-1.1%)	⬇️
...webserver/computation_comp_tasks_listening_task.py	87.6% <0.0%> (+2.2%)	⬆️

[sanderegg]

one question. is that SHA here forever? say this is 10.11.9. Say they overwrite 10.11.9 with a new image (not saying this will happen with postgres, but it already happened with some other images), what happens to this SHA? it will change. is the old one still available forever or does it get pruned out by the dockerhub registry when cleaning out?

[GitHK]

The idea behind the sha256 is that if they overwrite the 10.11 tag (because tags are mutable), the sha256 layer is still there and you can pull it. I don't think that docker hub deletes these layers.

[pcrespov]

👍