Jinemi/thermograph
4
0
Fork 0
Code Issues 2 Pull requests 3 Projects Releases Packages Wiki Activity Actions

Promote dev to main: daemon roll + Iceberg-backed lake query #41

Merged
admin_emi merged 2 commits from dev into main 2026-07-24 19:01:53 +00:00
Conversation 0 Commits 2 Files changed 6 +13 -7
1 changed files with 13 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit 578fb563a4 - Show all commits

16
infra/deploy/stack/deploy-stack.sh
View file

@ -166,13 +166,19 @@ else
echo "==> Rolling web + worker + lake to $BACKEND_IMAGE"
docker service update --with-registry-auth --detach=false --image "$BACKEND_IMAGE" "${STACK_NAME}_web"
docker service update --with-registry-auth --detach=false --image "$BACKEND_IMAGE" "${STACK_NAME}_worker"
# lake ships in the same image; a stack file predating it has no service
# yet — the next SERVICE=all stack deploy creates it, so don't fail here.
if docker service inspect "${STACK_NAME}_lake" >/dev/null 2>&1; then
docker service update --with-registry-auth --detach=false --image "$BACKEND_IMAGE" "${STACK_NAME}_lake"
# lake and daemon ship in the same image; a stack file predating either
# has no service yet — the next SERVICE=all stack deploy creates it, so
# don't fail here. The daemon especially must roll with web: they share
# the /internal/* contract, and a version skew between them is exactly
# what pinning one BACKEND_IMAGE_TAG exists to prevent (seen live: the
# first post-creation backend roll left the daemon a release behind).
for extra in lake daemon; do
if docker service inspect "${STACK_NAME}_${extra}" >/dev/null 2>&1; then
docker service update --with-registry-auth --detach=false --image "$BACKEND_IMAGE" "${STACK_NAME}_${extra}"
else
echo " (no ${STACK_NAME}_lake service yet; created on the next full stack deploy)"
echo " (no ${STACK_NAME}_${extra} service yet; created on the next full stack deploy)"
fi
done
;;
frontend)
echo "==> Rolling frontend to $FRONTEND_IMAGE"