coulomb/railiance-cluster
2
0
Fork 0
Code Issues Pull Requests Actions 2 Projects Releases Wiki Activity

feat(boundary): move Gitea Helm values to railiance-apps (T06)
Some checks failed
railiance-tests / smoke (push) Has been cancelled
Details

Browse Source 
gitea-values.sops.yaml relocated to railiance-apps/helm/ per
ADR-003 boundary rules — Gitea is S5, values belong in S5 repo.
Tombstone left in helm/MOVED.md. SCOPE.md updated to reflect
resolved violation.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Bernd Worsch
2026-03-27 13:23:41 +01:00
parent 9fc5a033d5
commit 595a043634
3 changed files with 6 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
SCOPE.md
View File

@@ -124,4 +124,4 @@ keywords: [backup, restore, age, encryption, k3s, state, helm, kubeconfig, disas
## Notes
Runs on COULOMBCORE (92.205.130.254). State Hub access via ops-bridge reverse tunnel — `bridge up state-hub-coulombcore` from the workstation (see ADR-004). Gitea is currently deployed here as a Helm release (boundary violation: architecturally belongs to S5 — migration pending).
Runs on COULOMBCORE (92.205.130.254). State Hub access via ops-bridge reverse tunnel — `bridge up state-hub-coulombcore` from the workstation (see ADR-004). Gitea Helm values were migrated to S5 (railiance-apps) in RAIL-HO-WP-0004-T06 — boundary violation resolved.