kcl-composition-validator

Validate KCL compositions by running the comprehensive validation script from repository root: ./scripts/validate-kcl-compositions.sh. This enforces formatting, syntax checks, and end-to-end render validation to catch CI failures and resource duplication early in your workflow.

KCL composition validation enforces three stages: formatting compliance with CI standards, syntax and logic correctness, and end-to-end render validation. It catches mutation patterns, enforces inline conditionals and single-line list comprehensions, and detects resource duplication before deployment.

Yes. Run a focused render check from infrastructure/base/crossplane/configuration: crossplane render examples/app-basic.yaml app-composition.yaml functions.yaml --extra-resources examples/environmentconfig.yaml > /tmp/rendered.yaml. This validates your KCL produces correct rendered resources without CI delay.

Run validation when editing infrastructure/base/crossplane/configuration/kcl modules, working with KCL compositions or Crossplane resources, or before commits touching .k files. Integrate with pre-commit hooks to catch issues early and prevent CI failures.

KCL validation enforces CI-enforced formatting standards including inline conditionals, single-line list comprehensions, and no trailing blank lines. These rules prevent syntax errors and ensure consistent code style across Crossplane configurations.

Yes. KCL validation integrates with Crossplane render pipelines and pre-commit validation workflows. It validates compositions against your Crossplane configuration and functions, working within standard infrastructure-as-code deployment processes.