handler settings


#1

Just pulled in the pagerduty.rb handler. I would like to set it up to
use different PD services via api_key.

The best option I see at the moment is to pass a key variable on the
command or service name.

And have something like - settings['pagerduty']['#{service}_key'],

Then add all the keys to the pagerduty config

This doesn't really play nice with the puppet module though.

Is there already an internal name I could use where the config to pull
the variable from is the name of the handler. i.e.

handler "servicea-pagerduty"

settings[handler]['api_key'],

{
  "servicea-pagerduty": {
    "api_key": "mykey"
  }
}

Thanks,

Matt


#2

Here’s a gist that includes mixlib CLI into the PD handler, so that the PD service api_key can be specified. This may not be drop-in ready (was using a custom parent class), but should be pretty close.

-Nick

···

On Wednesday, April 24, 2013 3:03:32 AM UTC-7, Matt wrote:

Just pulled in the pagerduty.rb handler. I would like to set it up to

use different PD services via api_key.

The best option I see at the moment is to pass a key variable on the

command or service name.

And have something like - settings[‘pagerduty’][’#{service}_key’],

Then add all the keys to the pagerduty config

This doesn’t really play nice with the puppet module though.

Is there already an internal name I could use where the config to pull

the variable from is the name of the handler. i.e.

handler “servicea-pagerduty”

settings[handler][‘api_key’],

{

“servicea-pagerduty”: {

"api_key": "mykey"

}

}

Thanks,

Matt


#3