Run "snap debug validate-seed" to do basic validation of the generated seed.yaml

(cherry picked from commit b208ded59ea9e54ad42bd071a39cebe2e4809aa4)

Signed-off-by: Iain Lane <iain.lane@canonical.com>
This commit is contained in:
Michael Vogt 2019-07-16 10:27:27 +01:00 committed by Iain Lane
parent 51ef72e5b9
commit 3b3fe0fce8
No known key found for this signature in database
GPG Key ID: E352D5C51C5041D4
2 changed files with 10 additions and 1 deletions

2
debian/control vendored
View File

@ -33,7 +33,7 @@ Depends: ${misc:Depends},
python3-software-properties,
qemu-utils,
rsync,
snapd,
snapd (>= 2.39),
squashfs-tools (>= 1:3.3-1),
sudo,
u-boot-tools [armhf arm64],

View File

@ -579,6 +579,15 @@ snap_preseed() {
touch "$CHROOT_ROOT/var/lib/snapd/seed/.snapd-explicit-install-stamp"
;;
esac
# Do basic validation of generated snapd seed.yaml, doing it here
# means we catch all the places(tm) that snaps are added but the
# downside is that each time a snap is added the seed must be valid,
# i.e. snaps with bases need to add bases first etc.
if [ -e chroot/var/lib/snapd/seed/seed.yaml ]; then
snap debug validate-seed "$CHROOT_ROOT/var/lib/snapd/seed/seed.yaml"
fi
}
is_live_layer () {