Read the issue-core pin from the Application for the ESO pre-check.

The 2026-11-07 founder pre-check stopped at expected_revision because verify-live still required the 2026-10-20 pin 186c817. Live issue-core is Synced and Healthy at the current Application targetRevision. The attended script and runbook now take that revision from the Application file. T06 stays waiting on the founder re-run.

Assistant: grok
Assistant-Session: 01a1b732-21dc-7ab3-b857-8436973c43a3
This commit is contained in:
codex 2026-11-07 19:37:03 +01:00
parent d64557e0cf
commit 46b456c27b
3 changed files with 8 additions and 4 deletions

View file

@ -37,7 +37,8 @@ DRAFT="$ROOT/argocd/railiance01/drafts/external-secrets.application.yaml"
STAMP="$(date -u +%Y%m%dT%H%M%SZ)"
EVID="$ROOT/docs/evidence/2026-10-21-eso-adoption-prep/attended-$STAMP"
CHECK=(python3 "$ROOT/scripts/eso_attended_checks.py")
ISSUE_REV=186c817b67d3919a64acdddbd3889e539841f946
ISSUE_APP="$ROOT/argocd/railiance01/applications/issue-core.application.yaml"
ISSUE_REV="$(python3 -c 'import sys,yaml; print(yaml.safe_load(open(sys.argv[1]))["spec"]["source"]["targetRevision"])' "$ISSUE_APP")"
ISSUE_URL=ssh://git@forgejo.coulomb.social:30022/coulomb/rapp-issue-core.git
SYNC_JSON='{"operation":{"initiatedBy":{"username":"rpf-wp-0044-t06"},"sync":{"revision":"0.16.1","prune":false,"syncOptions":["ServerSideApply=true"],"syncStrategy":{"apply":{"force":false}}}}}'
@ -74,7 +75,7 @@ EOF
[ "$DRY" = 1 ] || mkdir -p "$EVID"
WORK="$(mktemp -d)"; chmod 700 "$WORK"; trap 'rm -rf "$WORK"' EXIT
say "route=$KUBECTL_ROUTE dry_run=$DRY evidence=$EVID"
say "route=$KUBECTL_ROUTE dry_run=$DRY evidence=$EVID issue-core=$ISSUE_REV"
step kube get nodes -o name
say "1/6 fresh predecessor proofs (300 s window starts now)"