Generated Artifacts
Use this page when a change should have emitted files and you need to know which command owns them.
Generated output is part of the source tree contract in this repository. If an API, policy, renderer, or chart input changes, the matching generated artifacts must change in the same PR. Do not edit generated files directly.
Edit the source input and rerun the owning command. Manual edits to generated output will be overwritten and usually hide the real source of truth from the next reviewer.
Reference table
Quick reference
| If you changed | Regenerate with | Main CI verifier |
|---|---|---|
api/v1alpha1/*.go | make manifests generate | verify-generated |
api/v1alpha1/*.go comments or API shapes that affect docs | make api-reference | verify-generated |
| CRD, admission, or RBAC inputs that feed the chart | make helm-sync | verify-helm |
.ast-grep/policy/architecture-boundaries.yml | make generate-ast-rules | verify-arch-policy |
internal/adapter/config/*.go renderer behavior | make test-update-golden | test |
Artifact ownership
- Kubernetes CRDs and
zz_generated.deepcopy.gocome fromapi/v1alpha1/*.go. - API reference docs come from API types and comments.
- Helm chart sync output comes from CRD, policy, and RBAC source material.
- Golden HCL files come from renderer behavior in
internal/adapter/config/. - Ast-grep boundary rules come from
.ast-grep/policy/architecture-boundaries.yml.
Verify
Safe regeneration sweep
make manifests generate
make api-reference
make helm-sync
make generate-ast-rules
make test-update-golden
Use this when several change areas overlap or when CI tells you generated output drifted but the failing surface is not obvious yet.
After regeneration
You are reading the unreleased main docs. Use the version menu for the newest published release, or check the release notes for what is already out.
Was this page helpful?
Use Needs work to open a structured GitHub issue for this page. The Yes button only acknowledges the signal locally.