Command list-regions

Usage: juju regions [options] <cloud>

Summary:

Lists regions for a given cloud.

Options:

--format (= tabular)

Specify output format (json|tabular|yaml)

-o, --output (= "")

Specify an output file

Details:

Examples:

juju regions aws

See also:

add-cloud, clouds, show-cloud, update-clouds

Aliases:

list-regions

@owenrm

I am not too sure what you are after but the help output for ‘regions’ is a lot more comprehensive:

$ juju help regions
Usage: juju regions [options] <cloud>

Summary:
Lists regions for a given cloud.

Global Options:
--debug  (= false)
    equivalent to --show-log --logging-config=<root>=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:
--format  (= tabular)
    Specify output format (json|tabular|yaml)
-o, --output (= "")
    Specify an output file

Details:
Examples:

    juju regions aws

See also:
    add-cloud
    clouds
    show-cloud
    update-clouds

Aliases: list-regions

Thanks for the heads up @anastasia-macmood. But this is a direct import from the current documentation (https://docs.jujucharms.com/commands).

@anthonydillon,

This feels like a waste of your effort to import outdated information from jujucharms.com.

In addition that they are outdated, some commands and their help vary between Juju versions.

This effort needs to be better coordinated between our teams.

I am happy to go around and fix all these pages that you’ve imported but why cannot it be done up front?

I am also pondering the value of having CLI help on the webpage… outdated or not