Canonical Juju

Commands are missing --debug in the usage

Bug #1563933 reported by Matt Bruzek
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Medium
Unassigned

Bug Description

I noticed in that the juju bootstrap command is missing the --debug flag from the usage string.

We should describe this flag as many users may need to use --debug to properly report bugs from the field.

Are there any other flags that are not defined in bootstrap? Also the deploy command needs this.

Tags: helpdocs
Revision history for this message
Peter Matulis (petermatulis) wrote :

I believe all commands lack this option in their CLI help text. Please add this option to the help text for all commands that support it.

tags: added: helpdocs
Cheryl Jennings (cherylj)
Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 2.0-beta4
Revision history for this message
Peter Matulis (petermatulis) wrote :

Suggested template:

--debug (= false)
    Show debug output

Cheryl Jennings (cherylj)
summary: - The juju bootstrap command is missing --debug in the usage
+ Commands are missing --debug in the usage
Changed in juju-core:
milestone: 2.0-beta4 → 2.0.1
Canonical Juju QA Bot (juju-qa-bot)
affects: juju-core → juju
Changed in juju:
milestone: 2.0.1 → none
milestone: none → 2.0.1
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.0.1 → none
Revision history for this message
Anastasia (anastasia-macmood) wrote :

I am marking this one as a duplicate of bug # 1628151.
I believe that under that bug we will also address showing other "hidden" options that apply to all commands like --show-logs, etc..

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.