Skip to main content
Wait for a resource to reach a condition. The —for condition is required. The —timeout flag defaults to 5m. Set —timeout=0s to evaluate the current resource snapshot only and exit without watching for changes. Supported resources and conditions:
  • pod: started, ready, complete, deleted
  • sandbox: started, ready, deleted
  • job: started, complete, deleted
  • deployment: started, ready, deleted
  • replicaset: started, ready, deleted
  • namespace: deleted
  • workspace: deleted
  • fleet: ready, condition=<name>
  • fleet-lease: fulfilled, condition=<name>
  • cloud-account: connected, condition=<name>
Workloads and workspaces are addressed by name within a namespace; a namespace is addressed by name alone and takes no —workspace; capacity resources are addressed by the 12-digit ID the platform assigned them. A namespace or a workspace is released asynchronously after ‘idyl namespace delete’ or ‘idyl workspace delete’ accepts the deletion. Waiting for deleted blocks until the platform has finalized the release and the name no longer resolves; while it is terminating the wait reports what still holds it back. Capacity resources report conditions — named properties, each with a reason from a closed set. —for=condition=<name> waits on one of them directly, for a property with no shorthand of its own: Attached, Launching, CapacitySatisfied fleet Accepted, Fulfilled fleet-lease Verified cloud-account Exit status says what happened, so a script can tell the three outcomes apart without reading any output. It means the same thing for every resource above: 0 the condition was reached 124 the deadline passed with the condition not yet reached; the resource may still reach it 125 the condition will not be reached — the workload failed or was deleted, or capacity reports something that has to change first: the resource’s own spec, the catalog it draws on, or the cloud account it provisions into 1 the command could not run: no session, an unknown resource, bad arguments The reason a wait ended is written to standard error whichever way it ended, so the status is what a script reads and the reason is what a person reads. Resource aliases match the rest of the CLI:
  • deployment, deployments, deploy
  • replicaset, replicasets, rs
  • pod, pods
  • job, jobs
  • sandbox, sandboxes
  • namespace, namespaces, ns
  • workspace, workspaces, ws
  • fleet, fleets
  • fleet-lease, fleet-leases, lease, leases
  • cloud-account, cloud-accounts

Usage

Commands

Flags

Inherited flags

Examples

Subcommand reference

idyl wait cloud-account

Wait for a cloud-account condition

Usage

Aliases

  • cloud-accounts

Flags

idyl wait deployment

Wait for a deployment condition

Usage

Aliases

  • deployments
  • deploy

Flags

idyl wait fleet

Wait for a fleet condition

Usage

Aliases

  • fleets

Flags

idyl wait fleet-lease

Wait for a fleet-lease condition

Usage

Aliases

  • fleet-leases
  • lease
  • leases

Flags

idyl wait job

Wait for a job condition

Usage

Aliases

  • jobs

Flags

idyl wait namespace

Wait for a namespace condition

Usage

Aliases

  • namespaces
  • ns

Flags

idyl wait pod

Wait for a pod condition

Usage

Aliases

  • pods

Flags

idyl wait replicaset

Wait for a replicaset condition

Usage

Aliases

  • replicasets
  • rs

Flags

idyl wait sandbox

Wait for a sandbox condition

Usage

Aliases

  • sandboxes

Flags

idyl wait workspace

Wait for a workspace condition

Usage

Aliases

  • workspaces
  • ws

Flags