Per-Manifest-Type Reference
tazuna.yaml’s manifests[].type can take four 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 / dependsOn / includes / tests), see tazuna.yaml schema - Manifest.
The former
type: parallelhas been removed in this refactor, replaced by thedependsOn-based DAG execution model. To run Manifests in parallel, line them up as ordinary Manifests and leavedependsOnempty; they fall into the same layer and run in parallel. See DAG Execution viadependsOnfor details.
Contents
kustomize— apply resources rendered by kustomizehelmfile— apply the result of helmfile templateoras— pull an artifact from an OCI registry and delegate to helmfile / kustomizegenesissecret— 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 |
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. |
genesissecret | GenesisSecret YAML file (unlike other types, a single file rather than a directory) |