juju-upgrade-mongo should ask for confirmation
Bug #1607766 reported by
Haw Loeung
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Wishlist
|
Unassigned | ||
Bug Description
Hi,
Just running juju-upgrade-mongo, it seems to perform the upgrade straight away. I was running it to see if it would print out some form of help or what it was going to do.
Perhaps it should print out some kind of confirmation before proceeding?
juju 2.0 beta3
Thanks,
Haw
| Changed in juju-core: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Martin Packman (gz) wrote | #1 |
| Changed in juju-core: | |
| status: | New → Triaged |
| tags: | added: cmdline usability |
| affects: | juju-core → juju |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
Interesting. I wonder if the style/expectation is changing on this. Historically upgrade-charm and upgrade-juju haven't prompted, only destroy-environment has, but with more interactive commands, perhaps more things need to prompt by default when -y is not passed.