coulomb/railiance-platform
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-platform/argocd/repositories
History
tegwick 60447e8b0a
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 5s
Details
Point issue-core ArgoCD Application at Forgejo Git source 
ArgoCD was still tracking gitea.coulomb.social, which lags Forgejo after the
registry migration. Sync issue-core workload manifests from forgejo.coulomb.social
so backend ConfigMap updates land on CoulombCore.

Also allow forgejo.coulomb.social in railiance-tenants AppProject sourceRepos.
2026-07-08 15:21:00 +02:00
..
issue-core.repository.sops.yaml.template Point issue-core ArgoCD Application at Forgejo Git source 2026-07-08 15:21:00 +02:00
railiance-platform.repository.sops.yaml.template Add ArgoCD GitOps bootstrap contract for railiance01 2026-06-19 21:05:12 +02:00
README.md Add ArgoCD GitOps bootstrap contract for railiance01 2026-06-19 21:05:12 +02:00

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