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>
20 lines
412 B
YAML
20 lines
412 B
YAML
kind: context
|
|
name: gitea-https
|
|
version: 1
|
|
description: "Gitea HTTPS: git credential helper + identity for token-based cloning and pushing"
|
|
requires: []
|
|
provides: [git-access]
|
|
|
|
git_identity:
|
|
name: "agent-runtimes"
|
|
email: "agent@oreillyit.nz"
|
|
|
|
scripts:
|
|
init: "./init.sh"
|
|
|
|
secrets_required:
|
|
- name: gitea-https
|
|
account_ref: "gitea-https"
|
|
mount_path: /run/agent/secrets/gitea-https
|
|
mode: "0400"
|