Referencerelease

release

Inspect and manage releases tracked by nyl apply.

Synopsis

nyl release <SUBCOMMAND> [OPTIONS]

Description

Every nyl apply records a release revision, storing the full rendered manifest and the set of applied resources in a Kubernetes Secret in the release namespace. The release subcommands let you inspect that history and roll back to a previous revision. Configure [release] history_limit in nyl.toml or pass nyl apply --history-limit to change how many revisions are kept (five by default; 0 keeps all). A successful rollback applies the nyl.toml limit too.

Subcommands

list - List all releases
show - Show details of a specific release
history - Show the revision history for a release
rollback - Roll back a release to a previous revision
delete - Delete release(s)

list

nyl release list [OPTIONS]

List tracked releases, optionally filtered by namespace.

show

nyl release show <NAME> --namespace <NAMESPACE> [OPTIONS]

Show the details of a release. By default the latest revision is shown; pass --revision <N> for a specific revision and --manifest to include the full rendered manifest.

history

nyl release history <NAME> --namespace <NAMESPACE> [OPTIONS]

Show the revision history of a release, including each revision’s status and timestamps.

rollback

nyl release rollback <NAME> --namespace <NAMESPACE> [OPTIONS]

Re-apply the manifest stored for a previous revision and record it as a new revision. Rollback reuses the same apply path as nyl apply: it applies the stored manifest with server-side apply, marks the previously deployed revision Superseded, and prunes resources that existed in the superseded revision but are not part of the rolled-back revision.

For example, if revision 4 is currently deployed, rolling back to revision 2 creates revision 5 whose content is identical to revision 2, marks revision 4 as Superseded, and removes any resources that revision 4 added on top of revision 2.

Options

-n, --namespace <NAMESPACE> - Release namespace (required)
-r, --revision <REVISION> - Revision to roll back to. Defaults to the revision immediately before the latest one (i.e. undo the most recent deployment).
-y, --yes - Skip the confirmation prompt
--context <CONTEXT> - Kubernetes context to use
--concurrency <N> - Maximum number of resources applied or pruned at the same time (default: 8; 1 applies serially). See nyl apply.
--history-limit <N> - Keep at most N release revisions, deleting the oldest after a successful rollback; 0 keeps every revision. Overrides [release] history_limit in nyl.toml.
--confirm-prune - Also prune resources whose sync option is Prune=confirm, as with nyl apply.

Examples

# Roll back to the revision before the current one (with confirmation)
nyl release rollback my-app --namespace default

# Roll back to a specific revision, skipping the confirmation prompt
nyl release rollback my-app --namespace default --revision 2 --yes

Notes

Rollback always creates a new revision rather than mutating history, so the full audit trail is preserved and a rollback can itself be rolled back.
Pruning matches nyl apply semantics: resources present in the previously deployed revision but absent from the rolled-back revision are deleted, unless their Argo CD sync options keep them.
A clear error is returned if the release or the requested revision does not exist, or if there is no previous revision to roll back to.

delete

nyl release delete <NAME>... --namespace <NAMESPACE> [OPTIONS]

Delete one or more releases (or a specific revision) and, by default, the resources they created. Like an Argo CD Application deletion, purging keeps resources whose sync option is Delete=false, and those with Delete=confirm, such as managed Namespaces, unless --confirm-delete is passed. See Pruning and deletion.

--no-purge - Delete only the release records, not the resources
--confirm-delete - Also delete resources whose sync option is Delete=confirm
--dry-run - Show what would be deleted without deleting it