You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(kubernetes): honor validate:false, surface real git errors, close schema gap
A field-test pass over the Kustomize GitOps delivery feature found four
real bugs, all fixed here:
- validate: false on a Kubernetes component was silently dropped during
stack processing and never reached any command: internal/exec's
Kubernetes comp-assembly copied provider/paths/manifests/render but
never validate. Threaded it through the full 3-layer merge (global ->
base component -> instance) via the same key-presence-safe
mergeComponentAnySection pattern paths/manifests already use (not
provider's zero-value pattern, which would be unsafe for a bool), plus
the matching --affected diffing and base-component cache entries.
- Git target errors (atmos kubernetes deploy/apply --target <git>) were
always opaque ("git clone (exit 128)", no cause) because the git
provisioner target never captured subprocess stderr, unlike the atmos
git command family. Moved the capture-and-hint machinery from cmd/git
into exported pkg/git symbols (CaptureStderr, WrapOperationError) so
both share one implementation, and wired it into the provisioner's
clone/commit/push calls.
- components.kubernetes.<name>.validate: false failed schema validation
("additionalProperties 'validate' not allowed') because the repo has
three hand-maintained copies of the stack-manifest JSON schema and the
original fix only patched one; atmos describe stacks/validate stacks
enforce a different copy. Patched the copy that's actually enforced and
added a regression test.
- A successful git-target delivery printed nothing at all, unlike cluster
apply and validate. Added a confirmation message.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
0 commit comments