Founder's Option A: argocd/railiance01/bootstrap (3 AppProjects, root with no automated block, tenants whitelist + postgresql.cnpg.io/Cluster), root path argocd/railiance01/applications (README placeholder, renders zero children), pinned child drafts in argocd/railiance01/drafts (issue-core repointed to rapp-issue-core manifests), rapp-issue-core repository template; issue-core template marked obsolete. argocd/bootstrap and argocd/applications untouched (coulombcore). Nothing applied. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 63291@bnt-lap001 Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703 |
||
|---|---|---|
| .. | ||
| issue-core.repository.sops.yaml.template | ||
| railiance-platform.repository.sops.yaml.template | ||
| rapp-issue-core.repository.sops.yaml.template | ||
| README.md | ||
ArgoCD Repository Registration
ArgoCD discovers Git repositories from Kubernetes Secrets in the argocd
namespace with argocd.argoproj.io/secret-type: repository.
Use the templates in this directory to create SOPS-encrypted, non-plaintext repository Secret files. Credentials must be sourced from the approved operator/OpenBao path and must never be committed in plaintext.
Recommended OpenBao path:
platform/operators/argocd/repositories/<repo-name>
After creating an encrypted file such as
argocd/repositories/railiance-platform.repository.sops.yaml, apply it with:
ARGOCD_REPOSITORY_SECRET=argocd/repositories/railiance-platform.repository.sops.yaml \
make argocd-repo-apply