E2E smoke test: verify full merge-to-deploy pipeline

### Type Feature ### Lineage Standalone — created as validation ticket for production-pipeline project 2026-05-24. ### Repo `ldraney/palinks` ### User Story As a platform operator I want to verify the full merge-to-deploy chain works for palinks So that I can confirm the pipeline fixes (CMP, Image Updater) are working end-to-end ### Context palinks is the first service to validate the production pipeline after fixing CMP SOPS discovery and Image Updater write-back. Push a trivial change, watch all 5 links of the chain fire, confirm the app is live. ### File Targets Files to modify: - Any trivial change (e.g. a comment in `app/views/layouts/application.html.erb`) Files NOT to touch: - Infrastructure files — this is a pipeline validation, not a code change ### Acceptance Criteria - [ ] Push triggers Woodpecker build - [ ] Image pushed to Harbor with SHA tag - [ ] Image Updater writes new tag to pal-e-deployments - [ ] ArgoCD syncs (CMP decrypts secrets, kustomize renders) - [ ] Pod running with new image, readiness probe passing - [ ] `curl https://palinks.tail5b443a.ts.net` returns 200 ### Test Expectations - [ ] Watch Woodpecker pipeline: `mcp__woodpecker__list_pipelines` - [ ] Watch image updater logs: `kubectl logs -n argocd -l app.kubernetes.io/name=argocd-image-updater` - [ ] Watch ArgoCD sync: `kubectl get app palinks -n argocd` - [ ] Watch pod rollout: `kubectl get pods -n palinks` ### Constraints - Blocked by CMP SOPS discovery fix (`ldraney/pal-e-services #92`) - Blocked by image updater verification (`ldraney/pal-e-services #94`) ### Checklist - [ ] Trivial change pushed - [ ] All 5 pipeline links verified - [ ] Site accessible ### Related - `production-pipeline` — parent project - `ldraney/pal-e-services #92` — CMP fix (blocker) - `ldraney/pal-e-services #94` — Image Updater verification (blocker)

ldraney commented

2026-05-24 15:37:42 +00:00

Owner

Type

Feature

Lineage

Standalone — created as validation ticket for production-pipeline project 2026-05-24.

Repo

ldraney/palinks

User Story

As a platform operator
I want to verify the full merge-to-deploy chain works for palinks
So that I can confirm the pipeline fixes (CMP, Image Updater) are working end-to-end

Context

palinks is the first service to validate the production pipeline after fixing CMP SOPS discovery and Image Updater write-back. Push a trivial change, watch all 5 links of the chain fire, confirm the app is live.

File Targets

Files to modify:

Any trivial change (e.g. a comment in app/views/layouts/application.html.erb)

Files NOT to touch:

Infrastructure files — this is a pipeline validation, not a code change

Acceptance Criteria

Push triggers Woodpecker build
Image pushed to Harbor with SHA tag
Image Updater writes new tag to pal-e-deployments
ArgoCD syncs (CMP decrypts secrets, kustomize renders)
Pod running with new image, readiness probe passing
curl https://palinks.tail5b443a.ts.net returns 200

Test Expectations

Watch Woodpecker pipeline: mcp__woodpecker__list_pipelines
Watch image updater logs: kubectl logs -n argocd -l app.kubernetes.io/name=argocd-image-updater
Watch ArgoCD sync: kubectl get app palinks -n argocd
Watch pod rollout: kubectl get pods -n palinks

Constraints

Blocked by CMP SOPS discovery fix (ldraney/pal-e-services #92)
Blocked by image updater verification (ldraney/pal-e-services #94)

Checklist

Trivial change pushed
All 5 pipeline links verified
Site accessible

production-pipeline — parent project
ldraney/pal-e-services #92 — CMP fix (blocker)
ldraney/pal-e-services #94 — Image Updater verification (blocker)

Rows
Columns

E2E smoke test: verify full merge-to-deploy pipeline #8