From 52e8d6071bc1d1d92740e0e1bbdef4584f87edcd Mon Sep 17 00:00:00 2001
From: Achilleas Koutsou <achilleas@koutsou.net>
Date: Thu, 30 Jan 2025 18:35:59 +0100
Subject: [PATCH] test/filesystem: print blueprint contents when creating file

Can be useful for troubleshooting and tracing test logs.
---
 test/cases/filesystem.sh | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/test/cases/filesystem.sh b/test/cases/filesystem.sh
index d19763d7a1..7f49f32212 100755
--- a/test/cases/filesystem.sh
+++ b/test/cases/filesystem.sh
@@ -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"