letsbe
/
automated-setup
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

feat: support registration_token in JSON config 

Can now pass registration_token directly in JSON instead of
requiring SYSADMIN_REGISTRATION_TOKEN environment variable.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Matt 2025-12-07 12:28:08 +01:00
parent 850a46e5ea
commit f935f7057a
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
script/start.sh
View File

@ -31,7 +31,8 @@
# "skip_ssl": false,
# "customer": "acme",
# "domain": "acme.com",
# "company_name": "Acme Corp"
# "company_name": "Acme Corp",
# "registration_token": "uuid-from-orchestrator"
# }
#
@ -134,6 +135,10 @@ parse_json() {
COMPANY_NAME=$(echo "$json" | jq -r '.company_name // empty')
DOCKER_USER=$(echo "$json" | jq -r '.docker_user // empty')
DOCKER_TOKEN=$(echo "$json" | jq -r '.docker_token // empty')
# Registration token (can also be set via environment variable)
local json_token=$(echo "$json" | jq -r '.registration_token // empty')
[[ -n "$json_token" ]] && SYSADMIN_REGISTRATION_TOKEN="$json_token"
}
# =============================================================================