Files
pezkuwi-subquery/ops/host/subquery-deploy
T
Satoshi Qazi Muhammed 7ec6d9971f ci: deploy over a pinned, single-purpose key instead of root
deploy-vps reached subquery1 as root, through appleboy/ssh-action referenced
by tag, with a key whose comment (mamostehp@MamostePC) made it look like a
person's. It now uses plain ssh with SUBQUERY_DEPLOY_KEY, which the host pins
(authorized_keys restrict,command=) to ops/host/subquery-deploy-ssh: the
commit SHA is its only input. subquery-deploy, run through sudo, does what
the workflow's script did, with three changes:

- It deploys exactly the SHA CI was triggered for, and only a commit on main.
- The host's local edits to tracked files (the indexer manifests) are put
  back whether the deploy succeeds or fails. Before, a failed build exited
  before `stash pop` and left them stashed.
- Only tracked files are stashed. Stashing untracked ones too (.yarn/, which
  yarn install recreates) made every pop fail half-way; that is how 13 stash
  entries piled up on the host.

test-deploy.sh covers this against a scratch clone (red with the restore
trap removed); CI runs it with shellcheck. subquery1's host key is pinned.
The indexer endpoints themselves are unchanged. Actions pinned to SHAs; the
secret scanner's own AGPL licence is allowed in dependency review.
2026-10-09 06:57:03 +04:00

45 lines
1.7 KiB
Bash
Executable File

#!/bin/bash
# Brings /opt/subquery to a commit of main and rebuilds and restarts the
# compose stack (indexers, noter and payout bots). Installed root-owned at
# /usr/local/sbin/subquery-deploy; reached only through subquery-deploy-ssh.
#
# The host keeps local edits to tracked files (the indexer manifests point at
# a host-specific endpoint). They are stashed for the pull and always put
# back, whether the deploy succeeds or not. Only tracked files are stashed:
# stashing untracked ones too (.yarn/, which yarn install recreates) made
# every pop fail half-way and left a stash entry behind on each deploy.
set -euo pipefail
SHA="${1:-}"
if ! [[ "$SHA" =~ ^[0-9a-f]{40}$ ]]; then
echo "subquery-deploy: expected the 40-character commit SHA to deploy" >&2
exit 2
fi
cd /opt/subquery
stashed=
if ! git diff --quiet; then
git stash push -q -m "subquery-deploy $SHA"
stashed=1
fi
restore () {
if [ -n "$stashed" ]; then
git stash pop -q || echo "subquery-deploy: could not restore the host's local edits; they are in 'git stash list'" >&2
fi
}
trap restore EXIT
git fetch -q origin main
# Deploy exactly what CI tested, and only a commit that is on main.
git merge-base --is-ancestor "$SHA" origin/main || { echo "subquery-deploy: $SHA is not on main" >&2; exit 1; }
git merge -q --ff-only origin/main
[ "$(git rev-parse HEAD)" = "$SHA" ] || { echo "subquery-deploy: main is at $(git rev-parse --short HEAD), not ${SHA:0:7}; a newer deploy will follow" >&2; exit 1; }
yarn install --frozen-lockfile
./node_modules/.bin/subql codegen pezkuwi-governance.yaml
./node_modules/.bin/subql build pezkuwi.yaml
docker compose -f docker-compose.prod.yml build
docker compose -f docker-compose.prod.yml up -d
echo "subquery-deploy: deployed ${SHA:0:7}"