Custom Sensu Handlers to support a multi-tenant environment, allowing checks themselves to emit the type of handler behavior they need in the event json
This pins bundler to 1.x (since bundler 2.x requires newer ruby versions) and removes some older ruby/puppet versions we aren't using.
It also attempts to add puppet 4.5 to test against, although the PUPPET_VERSION environment variables in the build don't appear to have any effect, since puppet is pinned to a specific version (3.6.2) in the Gemfile anyway.
I would have added Ruby 2.3, but using that encounters an issue because the syck module has been removed from ruby core and put into a gem, but puppet still thinks it's available by default. Hopefully using a newer puppet would work to fix that, but It seems like when that was tried in the past it was reverted: https://github.com/Yelp/sensu_handlers/commit/3673595c1689aecedb7484eb9a5a7a60063927cb
@solarkennedy What was the previous problem with upgrading puppet or allowing for multiple versions that led to the revert?
This pins bundler to 1.x (since bundler 2.x requires newer ruby versions) and removes some older ruby/puppet versions we aren't using.
It also attempts to add puppet 4.5 to test against, although the
PUPPET_VERSIONenvironment variables in the build don't appear to have any effect, since puppet is pinned to a specific version (3.6.2) in theGemfileanyway.I would have added Ruby 2.3, but using that encounters an issue because the syck module has been removed from ruby core and put into a gem, but puppet still thinks it's available by default. Hopefully using a newer puppet would work to fix that, but It seems like when that was tried in the past it was reverted: https://github.com/Yelp/sensu_handlers/commit/3673595c1689aecedb7484eb9a5a7a60063927cb
@solarkennedy What was the previous problem with upgrading puppet or allowing for multiple versions that led to the revert?