test/aws.sh: remove enabling cloud-init and bash from the blueprint
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>
This commit is contained in:
parent
790393c54e
commit
a2342ecc5d
1 changed files with 1 additions and 7 deletions
|
|
@ -114,14 +114,8 @@ EOF
|
||||||
# Write a basic blueprint for our image.
|
# Write a basic blueprint for our image.
|
||||||
tee "$BLUEPRINT_FILE" > /dev/null << EOF
|
tee "$BLUEPRINT_FILE" > /dev/null << EOF
|
||||||
name = "bash"
|
name = "bash"
|
||||||
description = "A base system with bash"
|
description = "A base system"
|
||||||
version = "0.0.1"
|
version = "0.0.1"
|
||||||
|
|
||||||
[[packages]]
|
|
||||||
name = "bash"
|
|
||||||
|
|
||||||
[customizations.services]
|
|
||||||
enabled = ["sshd", "cloud-init", "cloud-init-local", "cloud-config", "cloud-final"]
|
|
||||||
EOF
|
EOF
|
||||||
|
|
||||||
# Prepare the blueprint for the compose.
|
# Prepare the blueprint for the compose.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue