railiance-platform/argocd/railiance01/applications/issue-core.application.yaml
codex 30c48cb993 issue-core: pin rapp-issue-core 11af3cb (wave-2 requests, ISSUE-WP-0008-T01)
Not synced. The Application has no automated sync; apply by a manual sync
after rapp-issue-core 11af3cb is pushed to Forgejo.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 276069@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
2026-10-22 00:04:50 +02:00

27 lines
966 B
YAML

# railiance01 issue-core (RPF-WP-0044-T04, adopted 2026-10-20 under D2 89f1058f + founder go).
# No automated sync, no finalizer. Read-only SSH deploy key: argocd/rapp-issue-core-repository.
# targetRevision: rapp-issue-core 11af3cb (wave-2 requests 5m/48Mi, ISSUE-WP-0008-T01; on top of 805e124 forge-http URL).
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: issue-core
namespace: argocd
labels:
app.kubernetes.io/part-of: railiance-gitops
railiance.io/domain: issue-core
annotations:
argocd.argoproj.io/sync-wave: "10"
spec:
project: railiance-tenants
source:
repoURL: ssh://git@forgejo.coulomb.social:30022/coulomb/rapp-issue-core.git
targetRevision: 11af3cbf359ba850c8a807d7cc8b369c037862df
path: manifests
destination:
server: https://kubernetes.default.svc
namespace: issue-core
syncPolicy:
syncOptions:
- CreateNamespace=true
- ApplyOutOfSyncOnly=true
- PruneLast=true