allow gem management to be disabled for all plugins

[ripienaar]

At present to disable gem management you have to set this on every module, we should have a setting here to disable gem and package management globally.

The likes of archlinux doesnt do gems, see choria-plugins/nettest-agent#6

[ripienaar]

@bastelfreak so about packaging of plugins.

The idea is that any user can write a plugin and package it with the same quality/features as the official ones, towards that there's mco plugin package which given a standard mco plugin layout will make a module/deb/rpm/etc

https://choria.io/docs/configuration/plugins/

There's generally no knobs to tweak, it's built using the template here https://github.com/choria-io/puppet-mcollective/tree/master/files/mcollective/pluginpackager/templates/aiomodule

However, if you do want to tweak things, you can make a puppet directory and whatever is in there will be copied into the module after the template is pressed, this way you can override bits that the template makes - or augment it by say adding plans to a plugin like here https://github.com/choria-plugins/puppet-agent/tree/master/puppet

The rakefiles I use to build these plugin modules will copy the README and a few others into the puppet dir example to make the nicer readmes we now have on the forge https://github.com/choria-plugins/puppet-agent/blob/master/Rakefile#L66

Anyway tl;dr so if you write plugins, you have a 1 command way to make a forge module exactly to the same quality as the ones I build.

[ripienaar]

Oh one additional tweak option - and I don't like this I will change it maybe - but see https://github.com/choria-plugins/puppet-agent/blob/master/.plugin.yaml

This is data that will be merged into the built module, this is how plugins like the puppet one allow these read only actions to be run for everyone right out of the box while policy is by default deny all