Handler config - under handler key, or as separate snippet? about sensu-chef HOT 3 CLOSED

Are you wanting general configuration to be utilized by multiple handlers? Then the config_snippet resources has always been the only choice, as far as LWRPs go.

If you want handler specific configuration you can* use the additional attribute as you suggested above, but you'll have to access a key/value with some nesting.

The whole config is available to handlers that use the sensu-plugin (sensu-handler) library via settings().

from sensu-chef.

Hi,
What I mean is - including the 'additional' attribute may now be considered the best-practice to configure handlers,
but it's not backward-compatible with anything in the community-plugins
(of course, for mysterious reasons still not everyone uses Chef ;-)

I'm not sure though whether we can/need to do anything about it.
Only "fix" I can think of is to override settings[], so it first searches inside the handler config and then the top-level config, but it's too much complexity and magic I guess.

This may be a small support issue and not much more. Maybe this is +1 nitpicking.

from sensu-chef.

General configuration snippets have grown on me, it does make sense for encapsulating settings for a third party service, eg. pagerduty. Probably nitpicking :)

from sensu-chef.