Two attended activity-core releases patched the live Application without committing the pin, so a hand sync of railiance-apps-root would have rolled activity-core back to ce9a8f8. Git now matches live (no sync run). make argocd-pin-drift compares all railiance01 child pins with live and is required before root syncs. informed-decision drift is flagged for its owner. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 244572@bnt-lap001 Assistant-Session: 3b235e1a-ae45-4d0f-ae70-17a9bd78ece8
1,013 B
railiance01 child Applications
Synced by railiance-apps-root on railiance01 (declared in
argocd/railiance01/bootstrap/), by hand only until RPF-WP-0044-T07.
This file is a placeholder: git does not keep an empty directory, and a
missing path is a ComparisonError in ArgoCD. ArgoCD's directory source reads
only *.yaml, *.yml and *.json, so this README renders to zero children.
Add a child Application here only as part of its RPF-WP-0044 adoption task,
with the founder's go-ahead: no automated block, no finalizer, and a pinned
targetRevision. A merge here plus a hand sync of the root is a live
production change on railiance01. Drafts wait in ../drafts/, which no root
syncs.
A release that changes a child's targetRevision commits that pin here in the
same change window, whether or not the live Application was patched directly.
Before any hand sync of the root, run make argocd-pin-drift; any DRIFT
line means the sync would roll that child back, so stop and reconcile first.