`juju get-constraints`

Usage:

juju get-constraints [options] <application>

Summary:

Displays machine constraints for an application.

Global Options:

--debug  (= false)

Equivalent to --show-log --logging-config==DEBUG

-h, --help  (= false)

Show help on a command or other topic.

--logging-config (= "")

Specify log levels for modules

--quiet  (= false)

Show no informational output

--show-log  (= false)

If set, write the log file to stderr

--verbose  (= false)

Show more verbose output

Command Options:

-B, --no-browser-login  (= false)

Do not use web browser for authentication

--format  (= constraints)

Specify output format (constraints|json|yaml)

-m, --model (= "")

Model to operate in. Accepts [:]|

-o, --output (= "")

Specify an output file

Details:

Shows machine constraints that have been set for an application with juju set- constraints.

By default, the model is the current model.

Application constraints are combined with model constraints, set with juju set-model-constraints, for commands (such as ‘deploy’) that provision machines for applications. Where model and application constraints overlap, the application constraints take precedence.

Constraints for a specific model can be viewed with juju get-model- constraints.

Examples:

juju get-constraints mysql
juju get-constraints -m mymodel apache2

See also:

set-constraints
get-model-constraints
set-model-constraints