Hi Folks, There is currently a PR against stdlib that I am writing to you today about: https://github.com/puppetlabs/puppetlabs-stdlib/pull/444 Thanks to Spredzy for making this PR.
This is tracked in jira: https://tickets.puppetlabs.com/browse/MODULES-1982 This pattern has poked up a few different places. As the PR says, it has shown up in the monogodb module and the puppetdb module. I know that Michael Chapman added something like this to his OpenStack things and Dan Bode as well. At the modules triage today we had the following reactions (please reply if there is something you said I didn't get): * This is a new pattern * Having it in stdlib means we can't iterate on it quickly * This is a library thing, and should be a library * Once standardized, puppetdb and other modules could be retrofitted to use it * This will probably change frequently as people use it and explore what it should/can do We had the idea that rather than landing this in puppet-stdlib, that we could create a module in puppet-community to hold this and other validation/health check resources. We had some ideas on the name: puppet-healthcheck puppet-validation puppet-external_validate. It's worth noting that these are primitives for building multi-node orchestration with Puppet. What do you think? Do you use these patterns? Would you? What would you want from your library? Thanks, Spencer -- Spencer Krum n...@spencerkrum.com -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/1431630674.2625129.268922745.5AA0382C%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout.
