To ensure that the script fails when any command fails, it's recommended to set the set -e
option at the beginning of the script. This will make the script exit immediately if a
command exits with a non-zero status.

add-machineid.sh [1]

 #!/bin/bash
+set -e
 

It is a good practice to quote variables in shell scripts to prevent globbing and word
splitting. This is particularly important when variables are used in commands that might
fail or behave unexpectedly with certain inputs.

add-machineid.sh [9]

-docker exec $container sh -c "echo $unique_id > /etc/machine-id"
+docker exec "$container" sh -c "echo $unique_id > /etc/machine-id"
 

The URL used in the curl command should be verified for correctness as it appears to be a
development utility that might not be intended for production use. Ensure that the URL
points to a reliable and secure resource.

README.md [35]

-bash <(curl -s https://raw.githubusercontent.com/GlueOps/development-only-utilities/main/tools/aws/lightsail.sh)
+bash <(curl -s https://raw.githubusercontent.com/GlueOps/production-utilities/main/tools/aws/lightsail.sh)
 

The command for creating the cluster and adding the machine ID script is complex and might
be error-prone. Consider breaking it into multiple lines or adding comments for clarity.

README.md [29]

-curl https://raw.githubusercontent.com/GlueOps/k3d/main/k3d-config.yaml -o k3d-config.yaml && k3d cluster create --config k3d-config.yaml && bash <(curl -sL https://raw.githubusercontent.com/GlueOps/k3d/main/add-machineid.sh)
+curl https://raw.githubusercontent.com/GlueOps/k3d/main/k3d-config.yaml -o k3d-config.yaml
+k3d cluster create --config k3d-config.yaml
+bash <(curl -sL https://raw.githubusercontent.com/GlueOps/k3d/main/add-machineid.sh)