Per-Manifest-Type Reference
tazuna.yaml’s manifests[].type can take 5 values. This section breaks each type into its own page, covering what path points to, type-specific fields, and apply / destroy / build behavior.
For the spec of common Manifest fields (name / path / type / tags / includes / tests), see tazuna.yaml schema - Manifest.
Contents
kustomize— apply resources rendered by kustomizehelmfile— apply the result of helmfile templateoras— pull an artifact from an OCI registry and delegate to helmfile / kustomizeparallel— process child Manifests in parallelgenesissecret— generate Kubernetes Secrets from a GenesisSecret YAML
Type-to-Specific-Field Correspondence
Each type has a corresponding options object inside manifests[]. Only the field corresponding to type is read; the others are ignored.
type | Specific field name | Field type |
|---|---|---|
kustomize | kustomize | ManifestKustomize |
helmfile | helmfile | ManifestHelmfile |
oras | oras | ManifestORAS |
parallel | parallel | ManifestParallel |
genesissecret | genesisSecret | Empty object (no fields in the current version) |
type: genesissecret is all lowercase, but the corresponding field name is genesisSecret (camelCase). YAML keys are uniformly camelCase, and only the value of type is a plain identifier (all lowercase).
Type-to-path Correspondence
path is interpreted as a path relative to the directory in which tazuna.yaml itself resides. What it should point to differs by type.
type | What path points to |
|---|---|
kustomize | A directory containing kustomization.yaml |
helmfile | A directory containing helmfile.yaml |
oras | Not used in practice. Cannot be empty due to validation, so write any directory. |
parallel | Not used in practice. The path from children[] is used. It cannot be empty due to validation. |
genesissecret | GenesisSecret YAML file (unlike other types, a single file rather than a directory) |