hull releases status

Synopsis

hull releases status reports where each release in your hull-releases.yaml currently stands — its latest revision and status — one line per release. It is the quick “is the whole set up, and at which revision?” check.

When to use it

After an install or upgrade, to confirm every release landed.
As a routine health check on the set, or a CI gate: a release that was never installed shows plainly as not deployed.

What happens

Reads the spec file (--file, default hull-releases.yaml) for the list of release names.
Looks up each release’s latest recorded revision in the cluster (using -n/--namespace and the global cluster flags).
Prints one line per release, in the order they appear in the file: name: revision N status=... for a recorded release, or name: not deployed for one with no record.

Releases are reported in file order, not dependency order. A reachable cluster is required, because the release records live there.

Usage

hull releases status [flags]

Flags

Flag	Type	Default	Effect
`--file`	string	`hull-releases.yaml`	read the spec from this path instead of the default

Inherits the global flags (--kube-context, --kubeconfig, -n/--namespace, --debug).

Worked example

INPUT — hull-releases.yaml. postgres and redis are installed; api was declared but never installed:

releases:
  - name: postgres
    package: ./charts/postgres
    namespace: data

  - name: redis
    package: ./charts/redis
    namespace: data

  - name: api
    package: ./charts/api
    namespace: apps
    dependsOn:
      - postgres
      - redis

COMMAND:

hull releases status

OUTPUT:

postgres: revision 1 status=deployed
redis: revision 1 status=deployed
api: not deployed

Each installed release shows its latest revision and status; api has no record in the cluster, so it reports not deployed — a signal to run hull releases install or upgrade.