feat(manage-server): add --local flag to upgrade.sh for redeploying an already-built image #22

Merged

amiryahaya merged 1 commit from sync-859-upgrade-local-image into main

2026-08-22 15:45:18 +02:00

amiryahaya commented

2026-08-22 13:38:30 +02:00

Owner

Distribution sync of amiryahaya/triton PR #860 (issue #859).

Summary

upgrade.sh always assumed a registry pull, so there was no way to run its triton-manage-bins volume-wipe safety step (needed since the volume is only auto-populated from the image on first container creation) against an already-built local image — relevant for anyone iterating on a locally-built manage-server image before a registry release.

--image TAG --local skips the registry pull and fails fast if TAG isn't already present locally. Everything else (pre-upgrade pg_dump, TLS bootstrap, triton-manage-bins wipe, container recreate, health check) is unchanged.

This is a pure sync — applied the same diff as the source-of-truth PR on top of this repo's copy, which already had a TRITON_MANAGE_JWT_SIGNING_KEY backfill block that the triton-repo source doesn't have (untouched by this change; flagging separately, not in scope here).

Test plan

bash -n + shellcheck clean
Diff-verified: only the intended --local change applied, no other lines touched
Source-of-truth version already validated end-to-end against a live manage-server deployment (see amiryahaya/triton#860's test plan)

🤖 Generated with Claude Code

Distribution sync of amiryahaya/triton PR #860 (issue #859). ## Summary `upgrade.sh` always assumed a registry pull, so there was no way to run its `triton-manage-bins` volume-wipe safety step (needed since the volume is only auto-populated from the image on first container creation) against an already-built local image — relevant for anyone iterating on a locally-built manage-server image before a registry release. `--image TAG --local` skips the registry pull and fails fast if `TAG` isn't already present locally. Everything else (pre-upgrade `pg_dump`, TLS bootstrap, `triton-manage-bins` wipe, container recreate, health check) is unchanged. This is a pure sync — applied the same diff as the source-of-truth PR on top of this repo's copy, which already had a `TRITON_MANAGE_JWT_SIGNING_KEY` backfill block that the triton-repo source doesn't have (untouched by this change; flagging separately, not in scope here). ## Test plan - [x] `bash -n` + `shellcheck` clean - [x] Diff-verified: only the intended `--local` change applied, no other lines touched - [x] Source-of-truth version already validated end-to-end against a live manage-server deployment (see amiryahaya/triton#860's test plan) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

amiryahaya added 1 commit

2026-08-22 13:38:30 +02:00

feat(manage-server): add --local flag to upgrade.sh for redeploying an already-built image 534d7a29a9

Sync of amiryahaya/triton PR #860 (issue #859) — see that repo's
scripts/deploy/manage-server/upgrade.sh for the source-of-truth
version and full rationale.

--image TAG --local skips the registry pull and fails fast if TAG
isn't already present locally, but keeps the existing
triton-manage-bins volume-wipe and health-check safety steps intact.

amiryahaya merged commit 89ede7c3d5 into main

2026-08-22 15:45:18 +02:00

amiryahaya referenced this pull request from a commit

2026-08-22 15:45:19 +02:00

Merge pull request 'feat(manage-server): add --local flag to upgrade.sh for redeploying an already-built image' (#22) from sync-859-upgrade-local-image into main