-
Two fixes for a fresh `./setup.sh` install, plus the SSH jump host promoted
released this
2026-08-01 17:48:46 +00:00 from an opt-in component to a core part of the stack.
-
setup.sh— fresh installs aborted silently right afterMinting per-app OpenBao tokens. Theenv_gethelper'sgrep | cutpipeline returns
non-zero underset -euo pipefailwhen.envexists (it's created earlier
by the root-VAULT_TOKENenv_upsert) but a given app-token key is absent —
the normal first-run state. The unguardedexisting="$(env_get ...)"then
trippedset -eand killed the script before any token was minted.env_get
now always returns 0 (|| true), so "key absent" resolves to empty and the
run continues through token minting, the SSO/proxy bring-up, and the jump
host. Reproduced + verified the fix under the exact fresh-install condition. -
setup.sh—JUMP_VAULT_TOKENis now always minted (jump host is core;
the mint was already unconditional, this just documents it). -
jump host is no longer optional — it is built + started on every run,
with noCFG_JUMP_HOST_ENABLEDflag.docker-compose.yml: removedprofiles: ["jump-host"]from the
jump-hostservice sodocker compose upincludes it unconditionally.
The test-onlyldap-test-hostdownstream fixture keeps an opt-in profile,
renamedjump-host→ldap-test(docker compose --profile ldap-test up).setup.sh:SUBMODULESalways includesjump-host; the build/start +
host-register + summary lines for the jump host are no longer wrapped in a
JUMP_ENABLEDguard; theCOMPOSE_PROFILESexport is gone.bootstrap/bootstrap.js: jump-host provisioning (mint API token + write
jump-secrets.js+ mirror into OpenBao) and its directory service record
now run unconditionally — noCFG_JUMP_HOST_ENABLEDgate.setup.env.example/docs/index.md/docs/quickstart.md: dropped the
"optional / enable withCFG_JUMP_HOST_ENABLED=true" wording; the
CFG_JUMP_HOSThostname override +JUMP_SSH_PORTremain.
Downloads
-