build(snap): update edgexfoundry snap base to core20

[siggiskulason]

This commit includes a number of updates to migrate the base to core20.

• postgres: updating postgres to 12.9 from 10.19. This update includes changes to the
  post-refresh hook to handle the three cases of a) new install, b) refresh from
  a postgres-10 version and c) refresh from a postgres-12 version

• snapcraft-preload: updates to use latest version and fixed cmake setup

• redis: make-install-var replaced with make-parameters

• kong-daemon: setpriv package replaced with util-linux

Signed-off-by: Siggi Skulason siggi.skulason@canonical.com

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md

PR Checklist

Please check if your PR fulfills the following requirements:

• I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
• I am not introducing a new dependency (add notes below if you are)
• I have added unit tests for the new feature or bug fix (if not, why?) See Add test for postgres refresh from v10 to v12 canonical/edgex-checkbox-provider#21
• I have fully tested (add details below) this the new feature or bug fix (if not, why?)
• I have opened a PR for the related docs change (if not, why?) N/A

Testing Instructions

Test by building the edgexfoundry snap and running a) checkbox tests and b) TAF tests to confirm that there are no regressions.

Test the refresh by doing
1: new install

sudo snap remove --purge edgexfoundry
sudo snap install ./edgexfoundry_2.2.0-dev.13_amd64.snap --dangerous

2: refresh from Ireland

sudo snap remove --purge edgexfoundry
sudo snap install edgexfoundry --channel=2.0/stable
sudo snap install ./edgexfoundry_2.2.0-dev.13_amd64.snap --dangerous

Expected result: This will fail, as the epoch has been updated to 6. We will provide a later build with a 6* epoch, which will contain the pre-refresh hook code required to upgrade.

3: refresh from current build

sudo snap remove --purge edgexfoundry
sudo snap install ./edgexfoundry_2.2.0-dev.13_amd64.snap --dangerous
sudo snap install ./edgexfoundry_2.2.0-dev.13_amd64.snap --dangerous

New Dependency Instructions (If applicable)

[siggiskulason]

This version passes:

• all TAF functional tests
• all TAF integration tests
• checkbox tests

[anonymouse64]

seems reasonable to me for the most part, but I do wonder if it's okay for us to just delete Postgres 10 database on refresh and create a fresh version 12 database...

I have not tested the changes locally

[farshidtz]

We'll need to increment the epoch from 5 to 6 in this PR to prevent upgrades from existing deployments that have Postgres 10 installed but no way to backup the data in preperation for the Postgres 12 restore. This is to avoid data loss resulted from replacing Postgres 10 with 12; see https://www.postgresql.org/docs/12/upgrading.html

In future, another snap would be created with epoch 6* to act as a bridge, based on the code before this PR, but including only the backup feature. That snap would be released to the latest track to provide a path for 2.0|2.1|2.2 to 2.2.x upgrades. Installations from the LTS 2.1 track will not be affected by this release.

For more details on how the epoch works: https://snapcraft.io/docs/snap-epochs

[farshidtz]

Thanks a lot @siggiskulason for the updates. It looks very good overall.

I've added a few suggestions inline.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[siggiskulason]

Thanks, @farshidtz for the review, I've pushed an update with the requested changes.

Also, for testing purposes, I've pushed this snap to the latest/edge/core-refresh branch, so it can be tested with

sudo snap install checkbox-edgexfoundry --devmode --edge
sudo DEFAULT_TEST_CHANNEL="latest/edge/core-refresh" checkbox-edgexfoundry.latest

and the checkbox test for this PR can be run using this channel