Test Template on Staging

Validate Helm chart template changes in oep-stg before merging to master and affecting prod tenants.

Purpose

Safely test changes to apps/laravel/templates/ or chart defaults on staging only. Prod Applications remain on master.

When to use

• Template changes that need staging soak before prod promotion
• Changes to values.yaml defaults
• New chart features being trialled in staging

Steps

1. Open a PR branch in unipuka-infra-ops (e.g. feat/reverb-redis-broker-tune)
2. Make template changes on the branch
3. In the ApplicationSet (bootstrap/applicationsets/laravel.yaml), change the oep-stg element's targetRevision from master to your PR branch name
4. Open a small follow-up PR to merge ONLY the ApplicationSet targetRevision change for oep-stg to master
5. Merge the follow-up PR - Argo CD now points oep-stg Application at your feature branch; prd Applications stay on master
6. Validate in oep-stg - run smoke script: bash scripts/smoke.sh oep-stg
7. When validated: merge original PR to master, then revert targetRevision for oep-stg back to master

Rollback

Revert the targetRevision change in the ApplicationSet back to master. oep-stg reverts to master chart.

V&V

• argocd app get oep-stg-laravel shows targetRevision: feat/... (not master)
• argocd app get mansety-prd-laravel still shows targetRevision: master
• All oep-stg workloads healthy on the feature branch template