From a2342ecc5ded761066adf768a5b5a5ba8be76fe2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ond=C5=99ej=20Budai?= <ondrej@budai.cz>
Date: Mon, 5 Jun 2023 18:38:48 +0200
Subject: [PATCH] test/aws.sh: remove enabling cloud-init and bash from the
 blueprint
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

cloud-init and bash should be everywhere. Thus, there's no point in specifying
them as a customization. Actually, it might mask error if we ever stop
installing bash/enabling cloud-init.

Signed-off-by: Ondřej Budai <ondrej@budai.cz>
---
 test/cases/aws.sh | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/test/cases/aws.sh b/test/cases/aws.sh
index 95466ddea..9bca4a1d5 100755
--- a/test/cases/aws.sh
+++ b/test/cases/aws.sh
@@ -114,14 +114,8 @@ EOF
 # Write a basic blueprint for our image.
 tee "$BLUEPRINT_FILE" > /dev/null << EOF
 name = "bash"
-description = "A base system with bash"
+description = "A base system"
 version = "0.0.1"
-
-[[packages]]
-name = "bash"
-
-[customizations.services]
-enabled = ["sshd", "cloud-init", "cloud-init-local", "cloud-config", "cloud-final"]
 EOF
 
 # Prepare the blueprint for the compose.