Maidn/maidn-cli
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

docs: explain legacy app registration migration

Browse source
This commit is contained in:
eding 2026-09-16 08:56:28 +02:00
parent 799a51b485
commit 97e7b59910
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/operations.md
View file

@ -63,6 +63,10 @@ registration PR. The registration is stored in
`base/tekton/apps/<app>.yaml`; Flux loads the source-owned `.tekton` path and `base/tekton/apps/<app>.yaml`; Flux loads the source-owned `.tekton` path and
the generic EventListener dispatches by Forgejo repository name. the generic EventListener dispatches by Forgejo repository name.
Existing registrations are never overwritten. Move a legacy source registration
to its canonical source in a separate reviewed cluster-repository PR before
onboarding that application.
After Flux reports the app Kustomization Ready, use Forgejo's hook test endpoint After Flux reports the app Kustomization Ready, use Forgejo's hook test endpoint
against a non-`main` ref and inspect the resulting PipelineRun. The command and against a non-`main` ref and inspect the resulting PipelineRun. The command and
read-only checks are in [Webhook Smoke Test](#webhook-smoke-test). read-only checks are in [Webhook Smoke Test](#webhook-smoke-test).