65fc400fcd
The accelerators/ai-enablement precedent uses the literal 'platform' space id — those credentials happen to live in the platform-owned CP accounts. For hatchmate the credentials live in a CP account owned by the hatchmate space, so the ref must be 'hatchmate.space:hatchmate'. Misnamed ref caused the dispatcher's account resolver to fail with 'no active account for AccountRef(name=hatchmate, scope=space:platform)', failing every review task in the W4 vertical slice within seconds of dispatch. After this lands and the next CRS sync (~5 min) refreshes the concepts PVC, the next auto-advance fire on dfc4358c should resolve the account and proceed through the working-repo clone with the per-org hatchmate key.
29 lines
774 B
YAML
29 lines
774 B
YAML
kind: context
|
|
name: gitea-ssh-hatchmate
|
|
version: 1
|
|
description: "Gitea SSH: clone/push via SSH key for gitea.oreillyit.nz (hatchmate org — agent working-repo key for hatchmate/hatchmate-agents)"
|
|
requires: []
|
|
provides: [git-access]
|
|
# HC-11: repos this layer's forge credential may push to (host-qualified; CRS-103 gate).
|
|
write_targets:
|
|
- "gitea.oreillyit.nz/hatchmate/*"
|
|
|
|
git_identity:
|
|
name: "agent-runtimes"
|
|
email: "agent@oreillyit.nz"
|
|
|
|
ssh_hosts:
|
|
- alias: gitea.oreillyit.nz-hatchmate
|
|
hostname: gitea.oreillyit.nz
|
|
user: git
|
|
identity_secret: GITEA_SSH_KEY
|
|
|
|
scripts:
|
|
init: "./init.sh"
|
|
|
|
secrets_required:
|
|
- name: gitea-ssh-hatchmate
|
|
account_ref: "hatchmate.space:hatchmate"
|
|
mount_path: /run/agent/secrets/gitea-ssh-hatchmate
|
|
mode: "0400"
|