Skip to content

fix: remove kubeconform and kustomize validation for fragment output#45

Merged
jorisjonkers-dev-agents[bot] merged 1 commit into
mainfrom
fix/deploy-artifact-remove-kubeconform-kustomize
Jul 9, 2026
Merged

fix: remove kubeconform and kustomize validation for fragment output#45
jorisjonkers-dev-agents[bot] merged 1 commit into
mainfrom
fix/deploy-artifact-remove-kubeconform-kustomize

Conversation

@jorisjonkers-dev-agents

Copy link
Copy Markdown
Contributor

Fragment output files are schema documents with a wrapper object (e.g. { kind: "KubernetesWorkloadFragment", manifests: [...] }), not bare Kubernetes YAML with apiVersion at the root. Kubeconform and kustomize always fail on this format. Render correctness is guaranteed by the deploy-config-schema CLI during step (8).

Fragment files (kubernetes-workload-fragment.yaml, etc.) are schema
documents with a wrapper object (e.g. { kind: "KubernetesWorkloadFragment",
manifests: [...] }), not bare Kubernetes YAML with apiVersion at the root.
Kubeconform and kustomize both require standard apiVersion/kind and always
fail on this format, producing spurious E_KUBECONFORM_FAILED errors.

Render correctness is enforced by the deploy-config-schema CLI itself
during fragment rendering in step (8).
@jorisjonkers-dev-agents jorisjonkers-dev-agents Bot added the type: bug Something is broken or behaving incorrectly. label Jul 9, 2026
@jorisjonkers-dev-agents jorisjonkers-dev-agents Bot merged commit 99dfaf6 into main Jul 9, 2026
5 checks passed
@jorisjonkers-dev-agents jorisjonkers-dev-agents Bot deleted the fix/deploy-artifact-remove-kubeconform-kustomize branch July 9, 2026 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: bug Something is broken or behaving incorrectly.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant