puppetlabs-toy-chest / chloride Goto Github PK

IIRC the Execute action has it's own messaging for commands it has executed, which overlaps with the output from the Host. We should figure out how we actually want to handle STDOUT/STDERR, and other messaging, in a non-redundant and configurable way.

We should simplify/automate the process of the initial SSH connection so an end-user doesn't need to use connect_ssh. Addititionally, the SSH key file verifification logic from the installer could probably be ported over as an action.

We need better docs, both comments in the code as well as docs on the site. If we added YARD, we could probably get an initial stab at both of those for the price of one.

I think it would be useful to add a Puppet action that would ensure puppet is installed, and then pass along the arguments given to puppet. In this way you could kick off puppet agent -t, install a package with puppet resource package or do any other one-time resource management supported by the RAL. A convenience method for installing modules would also be useful.

Chloride::Action::Puppet.new(host: host, cmd: "resource package nginx ensure=latest")
Chloride::Action::Puppet.new(host: host, cmd: "agent -t")

We'd want to ensure that the action works correctly with FOSS and PE. Not sure if we'd want to deal with 3.8 support initially.

Making it easy to query and use facter facts once the puppet-agent is installed would be useful.

Currently, we only support SSH. It would be great if we also supported WinRM so you could use one tool to handle all of your remote management needs with one lib. There is already a library for WinRM. We'd just need to add a special connection config for WinRM that could be passed in to the Host object.

Having i18n support for non-English speakers is a good thing.

Currently, if you want to multi-thread this library, you'd have to manage that yourself. We could add multi-threading support natively as an option you can enable/disable.