Remove -exec and add -config

-config uses a new thing I recently learned setting up my Raspberry Pi. This should make everything much simpler on the backend side of things and will be more user-friendly.

I'm also thinking of adding BP_xxx error codes, but that isn't final yet, so expect changes.

Well that was it from me again, thanks for checking out Blueprint.
This commit is contained in:
purple 2023-07-16 20:22:59 +02:00 committed by GitHub
parent dde406c580
commit 29f576dd68
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -56,21 +56,17 @@ source .blueprint/lib/parse_yaml.sh;
source .blueprint/lib/db.sh;
source .blueprint/lib/telemetry.sh;
# -exec
if [[ "$1" == "-exec" ]]; then
# -config
# usage: "cITEM=VALUE bash blueprint.sh -config"
if [[ "$1" == "-config" ]]; then
# Quoteless arguments.
# There should be an easier way to do this and will be added in the future.
ql1=$(echo "$1" | tr -d "'\\\n\r;");ql2=$(echo "$2" | tr -d "'\\\n\r;");ql3=$(echo "$3" | tr -d "'\\\n\r;");ql4=$(echo "$4" | tr -d "'\\\n\r;");ql5=$(echo "$5" | tr -d "'\\\n\r;");
# Update the telemetry id to argument.
if [[ $ql2 == "key" ]]; then
echo "$ql3" > .blueprint/data/internal/db/telemetry_id;
echo Command executed.;
exit 1;
# cTELEMETRY_ID
# Update the telemetry id.
if [[ $cTELEMETRY_ID != "" ]]; then
echo "$cTELEMETRY" > .blueprint/data/internal/db/telemetry_id;
fi;
echo Command not found.;
echo BP_100;
exit 1;
fi;