juju action commands require -e in the "wrong" place
Bug #1461605 reported by
Nate Finch
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
every other juju command takes -e as a parameter after the command, e.g. juju deploy -e <env> <name>. However, the action commands require -e to be after the action sub command, i.e. juju action do -e <env> <name>. Putting -e after juju action results in "error: flag provided but not defined: -e" This is inconsistent, which is annoying, but it also makes juju more difficult to write scripts for, because you can't just always dump -e <env> after the command name.
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: improvement |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
To post a comment you must log in.
It would actually be nice if -e were a global option like -v or --show-log.