fix: use bare kubectl exec target #554

Merged
coilyco-ops merged 1 commit from issue-513 into main 2026-07-15 05:43:59 +00:00
Member

This narrows the kubectl ward KDL guardfile to the bare exec target, so cli-guard keys off the tool name instead of one fixed absolute path. The kubectl allowlist behavior stays unchanged.

  • What changed: switched .ward/guardfile.kubectl.kdl from exec /usr/local/bin/kubectl to exec kubectl and softened the nearby comment
  • Why: match the cli-guard authoring shape for exec guardfiles and avoid implying the path is load-bearing
  • Validation: WARD_CONFIG_REF="file://${PWD}/.ward" ward doctor and ward exec pre-commit-all both passed locally

closes #513
ward.workflow: pull-request-and-merge

This narrows the kubectl ward KDL guardfile to the bare exec target, so cli-guard keys off the tool name instead of one fixed absolute path. The kubectl allowlist behavior stays unchanged. - What changed: switched `.ward/guardfile.kubectl.kdl` from `exec /usr/local/bin/kubectl` to `exec kubectl` and softened the nearby comment - Why: match the cli-guard authoring shape for exec guardfiles and avoid implying the path is load-bearing - Validation: `WARD_CONFIG_REF="file://${PWD}/.ward" ward doctor` and `ward exec pre-commit-all` both passed locally closes #513 ward.workflow: pull-request-and-merge
fix: use bare kubectl exec target
All checks were successful
ci / ward-doctor (pull_request) Successful in 39s
ci / gate (pull_request) Successful in 1m34s
aba7fedbf4
coilyco-ops deleted branch issue-513 2026-07-15 05:43:59 +00:00
Sign in to join this conversation.
No description provided.