juju is missing a list-plugins command

Bug #1628538 reported by Richard Harding
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju

Bug Description

Per report from Marco:

I've started building plugins again, starting with `juju watch-status`[0]. I wanted to test the --description flag in Juju but `juju help plugins` and a myriad of other commands (I guessed) didn't work (juju list-plugins, juju plugins, etc).

Do we plan on having the ability to list plugins in 2.0?

And with my own notes:

I agree that list-plugins is the right idea here and that means that plugins becomes a noun in our language.

What's interesting is that add/remove fall out because that installing/uninstalling. I think that show-plugin might be interesting to auto run the --description flag to bring it into CLI alignment with the new world order.

Revision history for this message
Richard Harding (rharding) wrote :

Additional feedback for when we look to address this:

From roger:
I don't think that we should
arbitrarily run all executables that happen to have a "juju-" prefix.
It's potentially dangerous (for example, note that although git relies heavily
on plugins, it doesn't execute a plugin until you explicitly name it).

Perhaps there could be a standard way for a plugin to provide
metadata about itself as a data file.

Revision history for this message
Richard Harding (rharding) wrote :

This needs to be snap ready as well.

Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.0.1 → none
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

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.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.