ci: add kustomize-validate-action as a PR check#2
Conversation
This repo had no PR checks at all — a malformed kustomization.yaml edit (e.g. the vpa-rollout batch, homelab#455) could merge clean and only surface once ArgoCD tried to sync it. Reuses the existing dvystrcil/kustomize-validate-action rather than a new one; ubuntu-latest since the action needs no cluster access. Automated by bin/add-pr-check.py (homelab#455).
|
Closing — this PR shouldn't have been opened. This repo is a fork of CrunchyData's upstream postgres-operator-examples, vendored purely as a reference for PGO manifests. The check that was added correctly fails, but for the wrong reason to enforce here: several example directories intentionally omit credential files (azure.conf, gcs-key.json, s3.conf — they're illustrative), and helm/install/templates/*.yaml are genuine Helm chart templates (Go template syntax), not standalone YAML. Per this account's own OSS-contribution norms, a fork keeps upstream's shape — we don't impose our own CI conventions on it. Root cause (bin/audit-pr-checks.py resolving forked/vendored repos as if they were dvystrcil-owned deploy targets) is being fixed upstream in homelab. |
1 participant
Adds the standard structural + offline-schema PR check (render every kustomization, validate with kubeconform) this repo was missing entirely.
Automated by
bin/add-pr-check.py(homelab#455) — opened by CI, not a live human/AI editing session.