supply_drop
supply_drop copied to clipboard
Preparing for 1.0
In preparation for 1.0, I'd like to make supply_drop much more opinionated about how it works. I'd like to deprecate some of the configuration variables we've collected over the past few months. Specifically:
-
parallel_rsync
- make it always parallel, to do only one server at a time, set the pool size to 1 -
puppet_syntax_check
- not performant enough, killing feature -
puppet_verbose
- I have never had the need to use it. You can still munge the parameters if you want more output -
puppet_stream_output
- always stream output, if you want grouped output, it will be in the log file -
puppet_write_to_file
- always write to a file
New Features:
- one log file per puppet run
- first-class support for vendoring puppet
- figure out a way to minimize the configuration needed to achieve this
- add tasks to install the requisite package
Better Testing
- Unit tests around the plugin
- Investigate a way to write full-stack tests against several flavors of OS using Virtual Box.