particle-os/debian-forge-composer
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

test/filesystem: print blueprint contents when creating file

Browse source 
Can be useful for troubleshooting and tracing test logs.
This commit is contained in:
Achilleas Koutsou 2025-01-30 18:35:59 +01:00 • committed by Simon de Vlieger
parent a237447ca0
commit 448b1e276d
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
test/cases/filesystem.sh
View file

@ -119,7 +119,7 @@ check_result () {
greenprint "🚀 Checking custom filesystems (success case)"
write_fs_blueprint() {
tee "$BLUEPRINT_FILE" > /dev/null << EOF
tee "$BLUEPRINT_FILE" << EOF
name = "custom-filesystem"
description = "A base system with custom mountpoints"
version = "0.0.1"
@ -209,7 +209,7 @@ EOF
}
write_plain_blueprint() {
tee "$BLUEPRINT_FILE" > /dev/null << EOF
tee "$BLUEPRINT_FILE" << EOF
name = "custom-filesystem"
description = "A base system with custom plain partitions"
version = "0.0.1"
@ -279,7 +279,7 @@ EOF
}
write_lvm_blueprint() {
tee "$BLUEPRINT_FILE" > /dev/null << EOF
tee "$BLUEPRINT_FILE" << EOF
name = "custom-filesystem"
description = "A base system with custom LVM partitioning"
@ -367,7 +367,7 @@ EOF
}
write_btrfs_blueprint() {
tee "$BLUEPRINT_FILE" > /dev/null << EOF
tee "$BLUEPRINT_FILE" << EOF
name = "custom-filesystem"
description = "A base system with custom btrfs partitioning"
@ -495,7 +495,7 @@ sudo composer-cli blueprints delete custom-filesystem > /dev/null
greenprint "🚀 Checking custom filesystems (fail case)"
# Write a basic blueprint for our image.
tee "$BLUEPRINT_FILE" > /dev/null << EOF
tee "$BLUEPRINT_FILE" << EOF
name = "custom-filesystem-fail"
description = "A base system with custom mountpoints"
version = "0.0.1"