hull workspace status

Synopsis

hull workspace status reads hull-workspace.yaml, looks up each member in the cluster, and prints one table row per member showing its namespace, current revision, and status. It is the quickest way to see whether every part of a workspace is deployed and at which revision.

When to use it

  • After an install or upgrade, to confirm every member converged.
  • As a routine health check on a workspace-managed platform.
  • To spot members that are declared but not yet deployed — they show as not deployed.

What happens

  1. Reads hull-workspace.yaml from --dir (default .) and orders the members by dependency.
  2. For each member, queries its namespace for the current release.
  3. Prints a table: member name, namespace, revision, and status.
  4. A member with no release shows - and not deployed; if its namespace cannot be reached, the row shows (client error).

Usage 

hull workspace status [flags]

Flags

Flag Type Default Description
--dir string . Directory containing hull-workspace.yaml. Point it elsewhere to check a workspace in another directory.

Inherits the global flags.

Worked example

INPUT — hull-workspace.yaml with two members, where api depends on postgres. postgres is deployed; api has not been installed yet:

apiVersion: hull/v1
defaults:
  namespace: apps
members:
  - name: postgres
    path: ./postgres
  - name: api
    path: ./api
    dependsOn: [postgres]

Run it:

hull workspace status

OUTPUT:

MEMBER                         NAMESPACE            REVISION   STATUS
postgres                       apps                 3          deployed
api                            apps                 -          not deployed

postgres is listed first (dependencies before dependents) and reports revision 3, deployed. api has no release, so its revision is - and its status is not deployed. Both rows show apps, inherited from defaults.namespace.

See also