The information in this doc is based on Juju version 3.5.5, and may not accurately reflect other versions of Juju.
See also: [wait-for model](wait-for model), [wait-for application](wait-for application), [wait-for machine](wait-for machine)
Summary
Wait for a unit to reach a specified state.
Usage
juju wait-for unit [options] [<name>]
Options
| Flag | Default | Usage |
|---|---|---|
-B, --no-browser-login |
false | Do not use web browser for authentication |
-m, --model |
Model to operate in. Accepts [<controller name>:]<model name>|<model UUID> | |
--query |
life==“alive” && workload-status==“active” | query the goal state |
--summary |
true | output a summary of the application query on exit |
--timeout |
10m0s | how long to wait, before timing out |
Examples
Waits for a units to be machines to be length of 1.
juju wait-for unit ubuntu/0 --query='len(machines) == 1'
Waits for the unit to be created and active.
juju wait-for unit ubuntu/0 --query='life=="alive" && workload-status=="active"'
Details
The wait-for unit command waits for the unit to reach a goal state. The goal state can be defined programmatically using the query DSL (domain specific language). The default query for a unit just waits for the unit to be created and active.
The wait-for command is an optimized alternative to the status command for determining programmatically if a goal state has been reached. The wait-for command streams delta changes from the underlying database, unlike the status command which performs a full query of the database.
The unit query DSL can be used to programmatically define the goal state for machine within the scope of the unit. This can be achieved by using lambda expressions to iterate over the machines associated with the unit. Multiple expressions can be combined to define a complex goal state.