tazuna init

Generates a minimal includes-based tazuna.yaml skeleton. It suits the first step of bringing a new repository or component under Tazuna management.

tazuna init [-f tazuna.yaml] [--force]

Behavior

1. If the output target (-f / --file-path, default tazuna.yaml) already exists and --force is not given, it exits with an error (so an existing file is not accidentally clobbered).
2. Writes tazuna.yaml with the following content and prints created: <path> to stdout.
   • Sets apiVersion / kind to the canonical values.
   • Pins spec.minimumSupportedTazunaVersion to the version of the tazuna that generated it. As a result, an older tazuna binary that tries to process this file stops with an error.
   • spec.manifests is empty ([]). A commented example for loading each component’s tazuna.yaml via includes is attached.

The generated skeleton (the version depends on the tazuna that generated it):

apiVersion: tazuna.pepabo.com/v1
kind: Tazuna
spec:
  # The minimum version (semver) of tazuna required to process this tazuna.yaml.
  # A tazuna binary below it exits with an error to prevent misapplication.
  minimumSupportedTazunaVersion: "1.4.0"
  # Load each component's tazuna.yaml via includes.
  # Add includes entries to manifests as in the example below.
  #
  #   manifests:
  #     - name: infra
  #       includes:
  #         - path: ./infra/tazuna.yaml
  #         - path: ./addons/tazuna.yaml
  manifests: []

The skeleton as generated passes tazuna check as-is.

About version pinning

• If the running tazuna has a semver version (a release build), that value is normalized and embedded into minimumSupportedTazunaVersion (a leading v is stripped).
• When run with a local build (a non-semver version such as dev), the placeholder 0.0.0 is embedded. Regenerate with a release build, or manually rewrite it to an appropriate version.

For the comparison rule of minimumSupportedTazunaVersion itself, see tazuna.yaml schema - minimumSupportedTazunaVersion.

Flag

In addition to global flags, the following are accepted.

No arguments are accepted.

Examples

tazuna init
tazuna init -f infra/tazuna.yaml
tazuna init --force

Related

• Meaning of the generated fields: tazuna.yaml schema
• How to use includes: tazuna.yaml schema - Using includes