remove-* aliases for destroy-service and destroy-machine
Bug #1261628 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
John A Meinel | ||
| 1.16 |
Fix Released
|
Low
|
John A Meinel | ||
| juju-core (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
| Saucy |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
[Impact]
None
[Test Case]
juju bootstrap
juju deploy mysql
juju remove-service mysql
#fail
[Impact]
Minimal - simple code change to add new aliases.
[Original bug report]
We've talked about wanting to use the syntax "remove-foo" rather than "destroy-foo" because it feels less apocalyptic.
However, we don't actually even have those aliases for destroy-machine and destroy-service.
They should be added as aliases in 1.16, but for the 1.18 series the official name of the commands should be Remove* and the aliases will be the Destroy* variants.
Related branches
lp:~jameinel/juju-core/1.16-remove-service-1261628
- Juju Engineering: Pending requested
-
Diff: 38 lines (+4/-1)3 files modifiedcmd/juju/destroymachine.go (+1/-1)
cmd/juju/destroyservice.go (+1/-0)
cmd/juju/main_test.go (+2/-0)
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in juju-core: | |
| assignee: | nobody → John A Meinel (jameinel) |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| milestone: | none → 1.17.1 |
| milestone: | 1.17.1 → 1.17.0 |
| Changed in juju-core: | |
| milestone: | 1.17.0 → 1.17.1 |
| Changed in juju-core: | |
| milestone: | 1.17.1 → 1.18.0 |
| description: | updated |
| Changed in juju-core (Ubuntu): | |
| status: | New → Fix Released |
| Changed in juju-core (Ubuntu Saucy): | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #2 |
Revision history for this message
| John A Meinel (jameinel) wrote Re: [Bug 1261628] Re: remove-* aliases for destroy-service and destroy-machine | #3 |
| Changed in juju-core: | |
| milestone: | 1.18.0 → 1.17.4 |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| Changed in juju-core (Ubuntu): | |
| status: | Fix Released → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in juju-core (Ubuntu): | |
| status: | Triaged → Fix Released |
| description: | updated |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #5 |
| Changed in juju-core (Ubuntu Saucy): | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
The change is trivial and viable as a 1.16 change, but we have to decide if we actually want to do it to the stable series. The associated branch does do the work.