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

(cherry picked from commit b208ded59e)

Signed-off-by: Iain Lane <iain.lane@canonical.com>
ubuntu/disco
Michael Vogt 6 years ago committed by Iain Lane
parent a1302a4a91
commit 2dbda09b6a
No known key found for this signature in database
GPG Key ID: E352D5C51C5041D4

2
debian/control vendored

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

@ -643,6 +643,15 @@ snap_preseed() {
touch "$CHROOT_ROOT/var/lib/snapd/seed/.snapd-explicit-install-stamp" touch "$CHROOT_ROOT/var/lib/snapd/seed/.snapd-explicit-install-stamp"
;; ;;
esac 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
} }
snap_from_seed() { snap_from_seed() {

Loading…
Cancel
Save