Orchestration

In development

Orchestration is in development. Environments, their state in Git, the nyl state and nyl lease commands, Command, OciImage, and Terraform and OpenTofu units, one environment’s runs with nyl plan, nyl reconcile (including --local runs, drift repair, and lifecycle work), and nyl status, recovery with nyl recover and nyl verify, and deletion with nyl teardown, nyl hold and nyl resume, nyl state delete, runs over several environments, and approvals are available. Kubernetes publication units are planned for M5. The roadmap tracks the milestones.

Orchestration makes Nyl a Git-driven reconciler for whole environments. Units such as commands, infrastructure configurations, container images, and Kubernetes publications run in dependency order, record their results in Git, and pass their outputs to the units that depend on them. Like everything in Nyl, a run takes one path whether it starts on a workstation or in CI.

Resources

Environment

Selects the units it runs and names where its state lives.

EnvironmentGroup

Gives several environments shared defaults.

Command

Runs a declared command as a unit.

OciImage

Builds a container image and records its digest.

Terraform

Manages infrastructure with Terraform.

OpenTofu

Manages infrastructure with OpenTofu.

Guides

Environments and state

How state is stored, protected by a lease, and supported by Git hosts.

Runs

How a run chooses its source commit, resolves references between units, decides what executes, and records the result.

Recovery

How a run takes over from one that died, what an uncertain unit is, how to recover it, and how drift is repaired.

Deletion and holds

How units leave an environment, how they are torn down, and how a hold freezes one.

Git storage

Every repository and ref orchestration reads and writes.