You're not selling me on this.... ;) <div class="gmail_quote"><div dir="ltr">On Tue, Oct 27, 2015, 4:01 PM Tim Penhey <<a href="mailto:tim.penhey@canonical.com">tim.penhey@canonical.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I can't help but draw parallels to the plugin system. There was considerable resistance to adding the ideas of plugins to Juju. It was added complexity that no one needed and could be done simply using existing executable scripts, like juju-foo. Tim On 28/10/15 07:33, Cory Johns wrote: > You can accomplish most of this with the existing plugin system. You > can't override existing commands, but you can easily create thin > wrappers around them with your desired default args, and given the > discussion around --no-aliases, it seems like this is actually a > benefit. And plugins provide an easy way to add more intelligent > handling of args, and also come with zero additional dev burden on core. -- Juju-dev mailing list <a href="mailto:Juju-dev@lists.ubuntu.com" target="_blank">Juju-dev@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/juju-dev</a> </blockquote></div>