juju env could be friendlier to scripts
Bug #1193244 reported by
Stuart Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Frank Mueller |
Bug Description
The 'juju env' and 'juju switch' commands output annotated, human readable text:
Current environment: "fooenv"
I suspect it would be just as readable and more friendly to scripting if just the raw environment name was emitted.
Related branches
lp:~themue/juju-core/054-env-more-script-friendly
- Juju Engineering: Pending requested
-
Diff: 180 lines (+39/-42)2 files modifiedcmd/juju/switch.go (+25/-22)
cmd/juju/switch_test.go (+14/-20)
Changed in juju-core: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
milestone: | none → 2.0 |
assignee: | nobody → Frank Mueller (themue) |
Changed in juju-core: | |
status: | Confirmed → Triaged |
Changed in juju-core: | |
importance: | Wishlist → High |
tags: | added: improvement |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
milestone: | 2.0 → 1.17.0 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Two different solutions:
1. simply always print 'fooenv' instead of 'Current environment: "fooenv"' or
2. add an argument (e.g. -r / --raw) so that the output stay as it is but with the argument the raw env name is printed.
I would prefer the second solution. So it stays user oriented an consistent with the -l / --list option for the listing of environment.