Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

RSS

chef_handler_sns (5) Versions 0.1.0

Installs and enables chef-handler-sns: A simple Chef report handler that reports status of a Chef run through Amazon SNS. Includes IAM roles support. Amazon SNS can send notifications by SMS, email, Amazon SQS queues or to any HTTP endpoint.

Berkshelf/Librarian
Policyfile
Knife
cookbook 'chef_handler_sns', '= 0.1.0'
cookbook 'chef_handler_sns', '= 0.1.0', :supermarket
knife cookbook site install chef_handler_sns
knife cookbook site download chef_handler_sns
README
Dependencies
Quality

Description

Chef cookbook to install and enable chef-handler-sns: A simple Chef report handler that reports status of a Chef run through Amazon SNS. Includes IAM roles support.

Amazon SNS can send notifications by SMS, email, Amazon SQS queues or to any HTTP endpoint.

Build Status

Requirements

Cookbooks:

  • xml
  • chef_handler

Attributes

<table> <tr> <td>Attribute</td> <td>Description</td> <td>Default</td> </tr> <tr> <td><code>node['chef_handler_sns']['topic_arn']</code></td> <td>AWS topic ARN name (required).</td> <td><em>required</em></td> </tr> <tr> <td><code>node['chef_handler_sns']['access_key']</code></td> <td>AWS access key (required, but will try to read it from ohai with IAM roles).</td> <td><em>calculated from ohai with IAM roles</em></td> </tr> <tr> <td><code>node['chef_handler_sns']['secret_key']</code></td> <td>AWS secret key (required, but will try to read it from ohai with IAM roles). We do not recomend using this attribute, it is better to use <a href="#chef_handler_snstopic_arn">the LWRP</a>.</td> <td><em>calculated from ohai with IAM roles</em></td> </tr> <tr> <td><code>node['chef_handler_sns']['token']</code></td> <td>AWS security token (read from ohai with IAM roles).</td> <td><em>calculated from ohai with IAM roles</em></td> </tr> <tr> <td><code>node['chef_handler_sns']['region']</code></td> <td>AWS region.</td> <td><em>calculated from ohai</em></td> </tr> <tr> <td><code>node['chef_handler_sns']['subject']</code></td> <td>Message subject string in erubis format.</td> <td><em>calculated</em></td> </tr> <tr> <td><code>node['chef_handler_sns']['body_template']</code></td> <td>Full path of an erubis template file to use for the message body.</td> <td><em>calculated</em></td> </tr> <tr> <td><code>node['chef_handler_sns']['nokogiri']</code><br/>    <code>['use_system_libraries']</code></td> <td>Prevent nokogiri from compiling libxml2 and libxslt and force to use the system libraries. Should decrease the installation time.</td> <td><code>true</code></td> </tr> <tr> <td><code>node['chef_handler_sns']['supports']</code></td> <td>Type of Chef Handler to register as, ie <code>:report</code>, <code>:exception</code> or <code>both</code>.</td> <td><code>{<br>  "exception" => true<br/>}</code></td> </tr> <tr> <td><code>node['chef_handler_sns']['version']</code></td> <td>chef-handler-sns gem version to install.</td> <td><em>latest stable</em></td> </tr> </table>

Recipes

chef_handler_sns::default

Installs and enables the Chef SNS Handler.

Resources

chef_handler_sns[topic_arn]

Installs and enables the Chef SNS handler.

chef_handler_sns actions

  • enable: Installs and enables the Chef Handler.

chef_handler_sns attributes

<table> <tr> <td>Attribute</td> <td>Description</td> <td>Default</td> </tr> <tr> <td>topic_arn</td> <td>AWS topic ARN name (required).</td> <td><em>resource name</em></td> </tr> <tr> <td>access_key</td> <td>AWS access key (required, but will try to read it from ohai with IAM roles).</td> <td><code>node['chef_handler_sns']['access_key']</code></td> </tr> <tr> <td>secret_key</td> <td>AWS secret key (required, but will try to read it from ohai with IAM roles).</td> <td><code>node['chef_handler_sns']['secret_key']</code></td> </tr> <tr> <td>token</td> <td>AWS security token (read from ohai with IAM roles).</td> <td><code>node['chef_handler_sns']['token']</code></td> </tr> <tr> <td>region</td> <td>AWS region.</td> <td><code>node['chef_handler_sns']['region']</code></td> </tr> <tr> <td>subject</td> <td>Message subject string in erubis format.</td> <td><code>node['chef_handler_sns']['subject']</code></td> </tr> <tr> <td>body_template</td> <td>Full path of an erubis template file to use for the message body.</td> <td><code>node['chef_handler_sns']['body_template']</code></td> </tr> <tr> <td>nokogiri_use_system_libraries</td> <td>Prevent nokogiri from compiling libxml2 and libxslt and force to use the system libraries. Should decrease the installation time.</td> <td><code>node['chef_handler_sns']['nokogiri']</code><br/>    <code>['use_system_libraries']</code></td> </tr> <tr> <td>supports</td> <td>Type of Chef Handler to register as, ie <code>:report</code>, <code>:exception</code> or <code>both</code>.</td> <td><code>node['chef_handler_sns']['supports']</code></td> </tr> <tr> <td>version</td> <td>chef-handler-sns gem version to install.</td> <td><code>node['chef_handler_sns']['version']</code></td> </tr> </table>

AWS Credentials permissions

If you are using AWS IAM credentials or AWS IAM role credentials, they should have at least the following privileges:

{
  "Statement": [
    {
      "Sid": "Stmt1234",
      "Effect": "Allow",
      "Action": [
        "sns:Publish"
      ],
      "Resource": [
        "arn:aws:sns:us-east-1:12341234:MyTopicName"
      ]
    }
  ]
}

Usage Examples

Using Amazon IAM roles

Using chef_handler_sns cookbook with IAM roles is rather easy.

Including in a Cookbook Recipe

First, you need to include this cookbook as a dependency in your cookbook:

# metadata.rb
depends "chef_handler_sns"
# in your recipe
node["chef_handler_sns"]["topic_arn"] = "arn:aws:sns:us-east-1:12341234:MyTopicName"
include_recipe "chef_handler_sns::default"

Using the LWRP from a Cookbook Recipe

You can also use the chef_handler_sns LWRP directly instead of including the recipe:

# metadata.rb
depends "chef_handler_sns"
# in your recipe
chef_handler_sns "arn:aws:sns:us-east-1:12341234:MyTopicName"

Including in the Run List

To include this cookbook directly in your run list, you must set at least the topic_arn attribute:

{
  "name": "git.onddo.com",
  [...]
  "normal": {
    "chef_handler_sns": {
      "topic_arn": "arn:aws:sns:us-east-1:12341234:MyTopicName"
    }
  },
  "run_list": [
    [...]
    "recipe[chef_handler_sns]"
  ]
}

Passing the AWS credentials (machines without IAM roles)

If you are using Amazon EC2 without IAM roles or machines from other providers outside AWS, you must set the AWS credentials: access_key and secret_key (and sometimes also token).

Using the LWRP from a Cookbook Recipe

# metadata.rb
depends "chef_handler_sns"
# in your recipe
chef_handler_sns "arn:aws:sns:us-east-1:12341234:MyTopicName" do
  access_key "***AMAZON-KEY***"
  secret_key "***AMAZON-SECRET***"
end

Installing old versions

If you are not using IAM roles and you don't need to use AWS security tokens, you can use old versions of chef-handler-sns (< 1.0.0). Those versions does not require nokogiri, so they have lighter dependencies and take less time to install.

chef_handler_sns "arn:aws:sns:us-east-1:12341234:MyTopicName" do
  access_key "***AMAZON-KEY***"
  secret_key "***AMAZON-SECRET***"
  version "0.2.6"
end

Testing

Requirements

  • berkshelf ~> 2.0
  • chefspec ~> 3.2
  • test-kitchen
  • vagrant
  • kitchen-vagrant >= 0.10.0
  • foodcritic ~> 3.0

Running the syntax style tests

$ rake style

Running the integration tests

$ rake integration

Or:

$ kitchen test
$ kitchen verify
[...]

Running the unit tests

$ rake unit

Or:

$ rspec

ChefSpec matchers

enable_chef_handler_sns(topic_arn)

Assert that the Chef run enables chef_handler_sns.

topic_arn = "arn:aws:sns:us-east-1:12341234:MyTopicName"
resource = chef_run.chef_handler_sns(topic_arn)
expect(resource).to enable_chef_handler_sns(topic_arn).with(
  :topic_arn => topic_arn
)

Contributing

  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write you change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using Github

License and Author

Author: Xabier de Zuazo (xabier@onddo.com)
Copyright: Copyright (c) 2014 Onddo Labs, SL. (www.onddo.com)
License: Apache License, Version 2.0

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Dependent cookbooks

chef_handler >= 0.0.0
xml >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

No quality metric results found