Skip to content

Commit

Permalink
test/filesystem: print blueprint contents when creating file
Browse files Browse the repository at this point in the history
Can be useful for troubleshooting and tracing test logs.
  • Loading branch information
achilleas-k committed Feb 1, 2025
1 parent 0bae7a5 commit 21ca158
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions test/cases/filesystem.sh
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down Expand Up @@ -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"
Expand Down Expand Up @@ -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"
Expand Down Expand Up @@ -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"
Expand Down Expand Up @@ -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"
Expand Down

0 comments on commit 21ca158

Please sign in to comment.