Operations

This section collects guidance for continuously using Tazuna. For task-level procedures (“installing a new add-on,” “writing tazuna.yaml,” etc.), see Guides; for command and schema specifications, see the Reference.

This section focuses on operations that avoid incidents and operations that can detect drift.

Contents

• Operating tazuna destroy — the procedure to follow when running destroy on a production cluster, the two-layer guard of TAZUNA_DESTROY_EXECUTABLE and context_matches, and accident-prone scenarios.
• Drift Monitoring — operating tazuna state diff and tazuna state drift on a periodic schedule to visualize the two kinds of drift, output formats, and how to wire up notifications.
• CI Pipeline — the typical setup that runs check / build / plan on PRs and apply on main merges, where to place destroy, and choosing state-sync options.
• Observability — configuring OpenTelemetry trace export via --otlp-endpoint, the 3-layer trace tree, and the main span attributes.