coulomb/railiance-enablement
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Finish the railiance01 Argo CD declaration workplan.
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Has been cancelled
Details

Browse source 
Assistant: grok
Assistant-Session: 01a0d25d-d358-7e13-b84a-d007fbb7e34f
This commit is contained in:
tegwick 2026-09-24 09:56:54 +02:00
parent 7027f13178
commit 47c3bfa39a
1 changed files with 7 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

11
workplans/RAIL-EN-WP-0002-argocd-railiance01-declared-state.md
View file

@ -4,12 +4,12 @@ type: workplan
title: "Declare Argo CD Core on railiance01 and bound its resources" title: "Declare Argo CD Core on railiance01 and bound its resources"
domain: financials domain: financials
repo: railiance-enablement repo: railiance-enablement
status: active status: finished
flavor: implementation flavor: implementation
owner: codex owner: codex
topic_slug: railiance topic_slug: railiance
created: "2026-09-21" created: "2026-09-21"
updated: "2026-09-21" updated: "2026-09-24"
related: related:
- ArchitectureBlueprint-5.6 - ArchitectureBlueprint-5.6
- RPF-WP-0043 - RPF-WP-0043
@ -89,6 +89,9 @@ is empty.
## Not in this workplan ## Not in this workplan
Phase B (AppProjects, root app, per-application adoption) and phase C Phase B is `RPF-WP-0044` in railiance-platform. Phase C (retire coulombcore's
(retire coulombcore's ArgoCD) each need their own founder go-ahead. ArgoCD) stays with that later plan. Both need their own founder go-ahead.
Once phase B exists, ArgoCD's own manifest should move under GitOps too. Once phase B exists, ArgoCD's own manifest should move under GitOps too.
Both tasks here are done. The install is declared, and the resource bounds
were applied on 2026-09-21.