juju-core desperately needs man pages for tools
Bug #1186264 reported by
Andreas Hasenack
This bug affects 7 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
The juju-core project and package really need manpages for the tools. It's specially hard because you don't actually get the tools binaries bundled with the package, so you can't even run --help. Ironically enough, --help is available, but since the tools are only installed on a unit, you have to actually deploy something to get to --help...
You can use juju run config-get --help in a shell, to get the help output.
| description: | updated |
| tags: | added: doc |
| Changed in juju-core: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Changed in juju-core: | |
| status: | Confirmed → Triaged |
| tags: |
added: docs removed: doc |
| description: | updated |
| description: | updated |
| Changed in juju-core: | |
| importance: | High → Low |
| tags: | added: landscape |
Revision history for this message
| Cheryl Jennings (cherylj) wrote | #1 |
| Changed in juju-core: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
This is now available as the 'help-tool' command:
$ juju help-tool config-get
Usage: config-get [options] [<key>]
Summary:
print service configuration
Options:
-a, --all (= false)
print all keys
--format (= smart)
Specify output format (json|smart|yaml)
-o, --output (= "")
Specify an output file
Details:
When no <key> is supplied, all keys with values or defaults are printed. If
--all is set, all known keys are printed; those without defaults or values are
reported as null. <key> and --all are mutually exclusive.