bigjust / ansible-helga Goto Github PK

There is no (nice/programmatic) way to add more configurations to custom plugins.

The only way around this is to change the template directly, which is not ideal.

When using the role there should be a way to add configuration directives for any other plugin that doesn't require the user to change a template, but rather just an ansible playbook.

so that they aren't inserted as strings

When installing my custom plugin, I want to always grab the latest version. However, right now, as long as there is a version installed, Ansible's pip module is happy.

I'd like to figure out a way to optionally specify versions per plugin. This might not be possible without modifying Ansible module code, though, since when you give the version arg to the pip module, it always expects that variable to be something other than null.

I've played around with a few scenarios by adding different steps, but so far it looks like I'm duplicating work by installing the package more than once.

I'll also investigate whether this is a thing you can do with other Ansible package management modules.

Helga 1.7 added some new pllugins variables that would be useful to expose at the Ansble level.

These include:

• helga.settings.DISABLED_PLUGINS - blacklist of plugins not allowed to run (default is none; all plugins can run)
• helga.settings.ENABLED_PLUGINS - whitelist of plugins allowed to run (default is all plugins)
• helga.settings.DEFAULT_CHANNEL_PLUGINS - list of automatically enabled plugins in channels (old enabled_plugins value).

These are explained in depth here.

Also, most of the helga plugins originally included were separated out, so I think it makes sense to either add them as the default list of external plugins within the role, or to have some sort of default list that's auto-appended. A list of the removed plugins can be found in this commit

The goal would be to still include these, at the ansible level, as defaults, but update the machinery that makes that happen.