[chef] Using the wrapper cookbook development method to remove the pager duty contact from the Nagios Cookbook

[Joseph Hammerman < >]

Hi Chef users email distribution list,

I’m trying to use the wrapper development method to change the values written out for the contactgroups in the Nagios cookbook. As you all may or may not know, this cookbook makes heavy use of definitions, resources and LWRPs. Within the users_helper.rb definition file, the following block of code exists:

def return_user_contacts

    contacts = []

    # add base contacts from nagios_users data bag

    @users.each do |s|

      contacts << s['id']

    end

    # add pagerduty user if enabled

    contacts << 'pagerduty' unless @node['nagios']['pagerduty']['key'].empty?

    contacts

 end

I personally like to have an email only contactgroup.

I attempted this (which manipulates the arrays correctly):

http://pastebin.com/RVwBGa8f

My reasoning was that I have updated the information in the class members that are referenced when the file is rendered, so if I rerender the file, if the arrays contain the correct members, the file should be rendered with the content that I desire.

However, during the Chef run, I see this output:

Recipe: sm-nagios::_load_default_config

  * nagios_contactgroup[admins] action create (up to date)

  * nagios_contactgroup[admins-sms] action create (up to date)

I’m thinking I could be encountering the resource cloning that Chef does?

Can anyone assist in better understanding the method / process I should be using here?

Thanks all,

Joseph Hammerman

---------------------------------------------------------------------------

This message is intended only for the addressee. Please notify sender by e-mail if you are not the intended recipient. If you are not the intended recipient, you may not copy, disclose, or distribute this message or its contents to any other person and any such actions may be unlawful.
SecondMarket, Inc. (Member FINRA/SIPC, MSRB Registered) ("SecondMarket") does
not accept time sensitive, action-oriented messages or transaction orders, including orders to purchase or sell securities, via e-mail.
SecondMarket reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the SecondMarket e-mail system and archived in accordance with FINRA and SEC regulations.
This message is intended for those with an in-depth understanding of the high risk and illiquid nature of alternative assets and these assets may not be suitable for you. This message is not a solicitation for an order, and there is not enough information contained in this message in which to make an investment decision and any information contained herein should not be used as a basis for this purpose. SecondMarket does not produce in-house research, make recommendations to purchase or sell specific securities, provide investment advisory services, or conduct a general retail business.