juju unset succeeds without error when no options are specified
Bug #1247997 reported by
Ian Booth
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
"juju unset <servicename> " will appear to succeed even though no options to unset have been specified.
And, it makes a connection to the database, only then to close it again because there is nothing to do.
The command should print an error and exit early if no options are specified.
Related branches
lp:~wallyworld/juju-core/cli-api-unset
- Juju Engineering: Pending requested
-
Diff: 168 lines (+66/-20)6 files modifiedcmd/juju/unset.go (+10/-20)
cmd/juju/unset_test.go (+1/-0)
state/api/client.go (+9/-0)
state/api/params/params.go (+8/-0)
state/apiserver/client/client.go (+13/-0)
state/apiserver/client/client_test.go (+25/-0)
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
