Command 'juju bind'

See also: Binding, How to manage applications


juju bind [options] <application> [<default-space>] [<endpoint-name>=<space> ...]


Change bindings for a deployed 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

--force  (= false)

Allow endpoints to be bound to spaces that might not be available to all existing units

-m, --model (= "")

Model to operate in. Accepts [:]|


In order to be able to bind any endpoint to a space, all machines where the application units are deployed to are required to be configured with an address in that space. However, you can use the --force option to bypass this check.


To update the default binding for the application and automatically update all existing endpoint bindings that were referencing the old default, you can use the following syntax:

juju bind foo new-default

To bind individual endpoints to a space you can use the following syntax:

juju bind foo endpoint-1=space-1 endpoint-2=space-2

Finally, the above commands can be combined to update both the default space and individual endpoints in one go:

juju bind foo new-default endpoint-1=space-1

Last updated 9 months ago.