5f85d895c1
The CRS-served harnesses still carried `secrets_files: [{encrypted: true}]`
which now hard-fails on H-SECRET-1 ("SOPS-encrypted secrets_files entries
are no longer permitted") in the dispatcher's harness validator. Sync the
8 provider harnesses with the agent-runtimes copies: same `secrets_required`
shape, same `init.sh` (ESO-mounted file paths), same `bin/` wrappers.
Use bare `account_ref: "<provider>"` (not `<provider>.cp:cp` — that
scope-kind isn't valid per SR-DISP-1-FIELD).
Provider key names follow the per-provider schema as emitted by the CP
provisioner: minimax/airouter/z-ai → api_key; gitea-https/gitea-admin →
{token,base_url,username}; gitea-ssh* → {host,private_key}.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
22 lines
893 B
Bash
Executable File
22 lines
893 B
Bash
Executable File
#!/bin/bash
|
|
# gitea-ssh-accelerators init: copy the ESO-mounted SSH key to the path the
|
|
# harness-init `~/.ssh/config` expects (`IdentityFile /home/agent/.ssh/gitea-oreillyit-nz-accelerators`).
|
|
#
|
|
# Per H-SECRET-4: NO `export` of credentials. (The earlier draft set
|
|
# `GIT_SSH_COMMAND` here — a path, not a credential — but that export dies
|
|
# with the subshell and the harness-init's SSH config is the load-bearing
|
|
# path anyway.)
|
|
set -euo pipefail
|
|
|
|
SSH_KEY_SRC="/run/agent/secrets/gitea-ssh-accelerators/id_ed25519"
|
|
SSH_KEY_DST="/home/agent/.ssh/gitea-oreillyit-nz-accelerators"
|
|
|
|
if [ ! -r "$SSH_KEY_SRC" ]; then
|
|
echo "ERROR: SSH key not found at $SSH_KEY_SRC — ESO ExternalSecret not Ready?" >&2
|
|
exit 1
|
|
fi
|
|
|
|
mkdir -p /home/agent/.ssh
|
|
install -m 0600 -o agent -g agent "$SSH_KEY_SRC" "$SSH_KEY_DST"
|
|
echo "gitea-ssh-accelerators: SSH key staged at $SSH_KEY_DST (0600 agent:agent)"
|