juju help plugins lists plugins that are overridden by builtins
Bug #1389324 reported by
Aaron Bentley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
| juju-core |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
Where a plugin name is the same as a builtin name, juju will run the builtin, but it still lists the plugin in "juju help plugins". In this example, juju run is a plugin on my computer (In /usr/local/
$ PATH=./
ERROR 'juju-run --description': exit status 2
...
run error occurred running 'juju-run --description'
...
Since this is *not* the version of "juju run" that will actually be run if I type the command, it should not be listed. If anything is said about this plugin, it should be a warning that a builtin overrides it.
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | none → 2.1.0 |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
| Changed in juju: | |
| milestone: | 2.1-rc2 → none |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.