juju destroy-environment does not accept -e
Bug #1248329 reported by
Aaron Bentley
This bug affects 7 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Nate Finch | ||
Bug Description
destroy-environment has recently stopped accepting -e.
I understand the intent is to make environ an explicit parameter to prevent accidental destruction, but this breaks commandline compatibility, making it harder to test both 1.17 and 1.16 with the same set of scripts. As I noted in the similar --destination bug #1247175 1.17 must support -e. Presumably we can drop -e with 1.18 or 1.19
Related branches
lp://staging/~jameinel/juju-core/destroy-environment-e-1248329
- Juju Engineering: Pending requested
-
Diff: 93 lines (+50/-8)2 files modifiedcmd/juju/destroyenvironment.go (+24/-8)
cmd/juju/destroyenvironment_test.go (+26/-0)
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| tags: | added: destroy-environment ui |
| Changed in juju-core: | |
| milestone: | none → 1.17.1 |
| assignee: | nobody → Nate Finch (natefinch) |
| Changed in juju-core: | |
| milestone: | 1.17.1 → 1.18.0 |
| Changed in juju-core: | |
| status: | Triaged → Fix Committed |
| Changed in juju-core: | |
| milestone: | 1.18.0 → 1.17.2 |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
From Kapil's duplicate:
$ env | grep JUJU
JUJU_ENV=east
JUJU_HOME=/opt/juju
$ juju destroy-environment
error: no environment specified
Also a bit strange
$ juju destroy-environment -e east
error: flag provided but not defined: -e
This breaks existing scripts afaics