Version information
This version is compatible with:
- Puppet Enterprise 3.x
- Puppet 3.x
- , , ,
This module has been deprecated by its author since Sep 7th 2017.
The reason given was: This module has been moved to the care of Vox Pupuli where it is now being maintained and updated.
The author has suggested puppet-rabbitmq as its replacement.
Start using this module
Documentation
#rabbitmq
####Table of Contents
- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with rabbitmq
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
##Overview
This module manages RabbitMQ (www.rabbitmq.com)
##Module Description The rabbitmq module sets up rabbitmq and has a number of providers to manage everything from vhosts to exchanges after setup.
This module has been tested against 2.7.1 and is known to not support all features against earlier versions.
##Setup
###What rabbitmq affects
- rabbitmq repository files.
- rabbitmq package.
- rabbitmq configuration file.
- rabbitmq service.
###Beginning with rabbitmq
include '::rabbitmq'
##Usage
All options and configuration can be done through interacting with the parameters on the main rabbitmq class. These are documented below.
##rabbitmq class
To begin with the rabbitmq class controls the installation of rabbitmq. In here you can control many parameters relating to the package and service, such as disabling puppet support of the service:
class { '::rabbitmq':
service_manage => false,
port => '5672',
delete_guest_user => true,
}
Or such as offline installation from intranet or local mirrors:
class { '::rabbitmq':
key_content => template('openstack/rabbit.pub.key'),
package_gpg_key => '/tmp/rabbit.pub.key',
}
And this one will use external package key source for any (apt/rpm) package provider:
class { '::rabbitmq':
package_gpg_key => 'http://www.some_site.some_domain/some_key.pub.key',
}
Environment Variables
To use RabbitMQ Environment Variables, use the parameters environment_variables
e.g.:
class { 'rabbitmq':
port => '5672',
environment_variables => {
'RABBITMQ_NODENAME' => 'node01',
'RABBITMQ_SERVICENAME' => 'RabbitMQ'
}
}
Variables Configurable in rabbitmq.config
To change RabbitMQ Config Variables in rabbitmq.config, use the parameters config_variables
e.g.:
class { 'rabbitmq':
port => '5672',
config_variables => {
'hipe_compile' => true,
'frame_max' => 131072,
'log_levels' => "[{connection, info}]"
}
}
To change Erlang Kernel Config Variables in rabbitmq.config, use the parameters
config_kernel_variables
e.g.:
class { 'rabbitmq':
port => '5672',
config_kernel_variables => {
'inet_dist_listen_min' => 9100,
'inet_dist_listen_max' => 9105,
}
}
Clustering
To use RabbitMQ clustering facilities, use the rabbitmq parameters
config_cluster
, cluster_nodes
, and cluster_node_type
, e.g.:
class { 'rabbitmq':
config_cluster => true,
cluster_nodes => ['rabbit1', 'rabbit2'],
cluster_node_type => 'ram',
}
##Reference
##Classes
- rabbitmq: Main class for installation and service management.
- rabbitmq::config: Main class for rabbitmq configuration/management.
- rabbitmq::install: Handles package installation.
- rabbitmq::params: Different configuration data for different systems.
- rabbitmq::service: Handles the rabbitmq service.
- rabbitmq::repo::apt: Handles apt repo for Debian systems.
- rabbitmq::repo::rhel: Handles rpm repo for Redhat systems.
###Parameters
####admin_enable
Boolean, if enabled sets up the management interface/plugin for RabbitMQ.
####cluster_node_type
Choose between disk and ram nodes.
####cluster_nodes
An array of nodes for clustering.
####cluster_partition_handling
Value to set for cluster_partition_handling
RabbitMQ configuration variable.
####config
The file to use as the rabbitmq.config template.
####config_cluster
Boolean to enable or disable clustering support.
####config_kernel_variables
Hash of Erlang kernel configuration variables to set (see Variables Configurable in rabbitmq.config).
####config_mirrored_queues
DEPRECATED
Configuring queue mirroring should be done by setting the according policy for the queue. You can read more about it here
####config_path
The path to write the RabbitMQ configuration file to.
####config_stomp
Boolean to enable or disable stomp.
####config_variables
To set config variables in rabbitmq.config
####default_user
Username to set for the default_user
in rabbitmq.config.
####default_pass
Password to set for the default_user
in rabbitmq.config.
####delete_guest_user
Boolean to decide if we should delete the default guest user.
####env_config
The template file to use for rabbitmq_env.config.
####env_config_path
The path to write the rabbitmq_env.config file to.
####environment_variables
RabbitMQ Environment Variables in rabbitmq_env.config
####erlang_cookie
The erlang cookie to use for clustering - must be the same between all nodes. This value has no default and must be set explicitly if using clustering.
###key_content
Uses content method for Debian OS family. Should be a template for apt::source
class. Overrides package_gpg_key
behavior, if enabled. Undefined by default.
####ldap_auth
Boolean, set to true to enable LDAP auth.
####ldap_server
LDAP server to use for auth.
####ldap_user_dn_pattern
User DN pattern for LDAP auth.
####ldap_use_ssl
Boolean, set to true to use SSL for the LDAP server.
####ldap_port
Numeric port for LDAP server.
####ldap_log
Boolean, set to true to log LDAP auth.
####manage_repos
Boolean, whether or not to manage package repositories.
####management_port
The port for the RabbitMQ management interface.
####node_ip_address
The value of RABBITMQ_NODE_IP_ADDRESS in rabbitmq_env.config
####package_ensure
Determines the ensure state of the package. Set to installed by default, but could be changed to latest.
####package_gpg_key
RPM package GPG key to import. Uses source method. Should be a URL for Debian/RedHat
OS family, or a file name for RedHat OS family.
Set to http://www.rabbitmq.com/rabbitmq-signing-key-public.asc by default.
Note, that key_content
, if specified, would override this parameter for Debian OS family.
####package_name
The name of the package to install.
####package_provider
What provider to use to install the package.
####package_source
Where should the package be installed from?
On Debian- and Arch-based systems using the default package provider, this parameter is ignored and the package is installed from the rabbitmq repository, if enabled with manage_repo => true, or from the system repository otherwise. If you want to use dpkg as the package_provider, you must specify a local package_source.
####plugin_dir
Location of RabbitMQ plugins.
####port
The RabbitMQ port.
####service_ensure
The state of the service.
####service_manage
Determines if the service is managed.
####service_name
The name of the service to manage.
####ssl
Configures the service for using SSL.
####ssl_only
Configures the service to only use SSL. No cleartext TCP listeners will be created. Requires that ssl => true also.
####ssl_cacert
CA cert path to use for SSL.
####ssl_cert
Cert to use for SSL.
####ssl_key
Key to use for SSL.
####ssl_management_port
SSL management port.
####ssl_stomp_port
SSL stomp port.
####ssl_verify
rabbitmq.config SSL verify setting.
####ssl_fail_if_no_peer_cert
rabbitmq.config fail_if_no_peer_cert
setting.
####stomp_port
The port to use for Stomp.
####stomp_ensure
Boolean to install the stomp plugin.
####tcp_keepalive
Boolean to enable TCP connection keepalive for RabbitMQ service.
####version
Sets the version to install.
On Debian- and Arch-based operating systems, the version parameter is ignored and the latest version is installed from the rabbitmq repository, if enabled with manage_repo => true, or from the system repository otherwise.
####wipe_db_on_cookie_change
Boolean to determine if we should DESTROY AND DELETE the RabbitMQ database.
##Native Types
rabbitmq_user
query all current users: $ puppet resource rabbitmq_user
rabbitmq_user { 'dan':
admin => true,
password => 'bar',
}
Optional parameter tags will set further rabbitmq tags like monitoring, policymaker, etc. To set the administrator tag use admin-flag.
rabbitmq_user { 'dan':
admin => true,
password => 'bar',
tags => ['monitoring', 'tag1'],
}
rabbitmq_vhost
query all current vhosts: $ puppet resource rabbitmq_vhost
rabbitmq_vhost { 'myhost':
ensure => present,
}
rabbitmq_exchange
rabbitmq_exchange { 'myexchange@myhost':
user => 'dan',
password => 'bar',
type => 'topic',
ensure => present,
}
rabbitmq_user_permissions
rabbitmq_user_permissions { 'dan@myhost':
configure_permission => '.*',
read_permission => '.*',
write_permission => '.*',
}
rabbitmq_policy
rabbitmq_policy { 'ha-all@myhost':
pattern => '.*',
priority => 0,
applyto => 'all',
definition => {
'ha-mode' => 'all',
'ha-sync-mode' => 'automatic',
},
}
rabbitmq_plugin
query all currently enabled plugins $ puppet resource rabbitmq_plugin
rabbitmq_plugin {'rabbitmq_stomp':
ensure => present,
}
rabbitmq_erlang_cookie
This is essentially a private type used by the rabbitmq::config class to manage the erlang cookie. It replaces the rabbitmq_erlang_cookie fact from earlier versions of this module. It manages the content of the cookie usually located at /var/lib/rabbitmq/.erlang.cookie, which includes stopping the rabbitmq service and wiping out the database at /var/lib/rabbitmq/mnesia if the user agrees to it. We don't recommend using this type directly.
##Limitations
This module has been built on and tested against Puppet 3.x.
The module has been tested on:
- RedHat Enterprise Linux 5/6
- Debian 6/7
- CentOS 5/6
- Ubuntu 12.04/14.04
Testing on other platforms has been light and cannot be guaranteed.
Module dependencies
If running CentOS/RHEL, and using the yum provider, ensure the epel repo is present.
To have a suitable erlang version installed on RedHat and Debian systems, you have to install another puppet module from http://forge.puppetlabs.com/garethr/erlang with:
puppet module install garethr-erlang
This module handles the packages for erlang. To use the module, add the following snippet to your site.pp or an appropriate profile class:
For RedHat systems:
include 'erlang'
class { 'erlang': epel_enable => true}
For Debian systems:
include 'erlang'
package { 'erlang-base':
ensure => 'latest',
}
Downgrade Issues
Be advised that there were configuration file syntax and other changes made between RabbitMQ
versions 2 and 3. In order to downgrade from 3 to 2 (not that this is a terribly good idea)
you will need to manually remove all RabbitMQ configuration files (/etc/rabbitmq
) and
the mnesia directory (usually /var/lib/rabbitmq/mnesia
). The latter action will delete
any and all messages stored to disk.
Failure to do this will result in RabbitMQ failing to start with a cryptic error message about "init terminating in do_boot", containing "rabbit_upgrade,maybe_upgrade_mnesia".
##Development
Puppet Labs modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. We can’t access the huge number of platforms and myriad of hardware, software, and deployment configurations that Puppet is intended to serve.
We want to keep it as easy as possible to contribute changes so that our modules work in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
You can read the complete module contribution guide on the Puppet Labs wiki.
Authors
- Jeff McCune jeff@puppetlabs.com
- Dan Bode dan@puppetlabs.com
- RPM/RHEL packages by Vincent Janelle randomfrequency@gmail.com
- Puppetlabs Module Team
Types in this module release
2014-12-22 - Version 5.0.0
Summary
This release fixes a longstanding security issue where the rabbitmq erlang cookie was exposed as a fact by managing the cookie with a provider. It also drops support for Puppet 2.7, adds many features and fixes several bugs.
Backwards-incompatible Changes
- Removed the rabbitmq_erlang_cookie fact and replaced the logic to manage that cookie with a provider.
- Dropped official support for Puppet 2.7 (EOL 9/30/2014 https://groups.google.com/forum/#!topic/puppet-users/QLguMcLraLE )
- Changed the default value of $rabbitmq::params::ldap_user_dn_pattern to not contain a variable
- Removed deprecated parameters: $rabbitmq::cluster_disk_nodes, $rabbitmq::server::manage_service, and $rabbitmq::server::config_mirrored_queues
Features
- Add tcp_keepalive parameter to enable TCP keepalive
- Use https to download rabbitmqadmin tool when $rabbitmq::ssl is true
- Add key_content parameter for offline Debian package installations
- Use 16 character apt key to avoid potential collisions
- Add rabbitmq_policy type, including support for rabbitmq <3.2.0
- Add rabbitmq::ensure_repo parameter
- Add ability to change rabbitmq_user password
- Allow disk as a valid cluster node type
Bugfixes
- Avoid attempting to install rabbitmqadmin via a proxy (since it is downloaded from localhost)
- Optimize check for RHEL GPG key
- Configure ssl_listener in stomp only if using ssl
- Use rpm as default package provider for RedHat, bringing the module in line with the documented instructions to manage erlang separately and allowing the default version and source parameters to become meaningful
- Configure cacertfile only if verify_none is not set
- Use -q flag for rabbitmqctl commands to avoid parsing inconsistent debug output
- Use the -m flag for rabbitmqplugins commands, again to avoid parsing inconsistent debug output
- Strip backslashes from the rabbitmqctl output to avoid parsing issues
- Fix limitation where version parameter was ignored
- Add /etc/rabbitmq/rabbitmqadmin.conf to fix rabbitmqadmin port usage when ssl is on
- Fix linter errors and warnings
- Add, update, and fix tests
- Update docs
2014-08-20 - Version 4.1.0
Summary
This release adds several new features, fixes bugs, and improves tests and documentation.
Features
- Autorequire the rabbitmq-server service in the rabbitmq_vhost type
- Add credentials to rabbitmqadmin URL
- Added $ssl_only parameter to rabbitmq, rabbitmq::params, and rabbitmq::config
- Added property tags to rabbitmq_user provider
Bugfixes
- Fix erroneous commas in rabbitmq::config
- Use correct ensure value for the rabbitmq_stomp rabbitmq_plugin
- Set HOME env variable to nil when leveraging rabbitmq to remove type error from Python script
- Fix location for rabbitmq-plugins for RHEL
- Remove validation for package_source to allow it to be set to false
- Allow LDAP auth configuration without configuring stomp
- Added missing $ssl_verify and $ssl_fail_if_no_peer_cert to rabbitmq::config
2014-05-16 - Version 4.0.0
Summary
This release includes many new features and bug fixes. With the exception of erlang management this should be backwards compatible with 3.1.0.
Backwards-incompatible Changes
- erlang_manage was removed. You will need to manage erlang separately. See the README for more information on how to configure this.
Features
- Improved SSL support
- Add LDAP support
- Add ability to manage RabbitMQ repositories
- Add ability to manage Erlang kernel configuration options
- Improved handling of user tags
- Use nanliu-staging module instead of hardcoded 'curl'
- Switch to yum or zypper provider instead of rpm
- Add ability to manage STOMP plugin installation.
- Allow empty permission fields
- Convert existing system tests to beaker acceptance tests.
Bugfixes
- exchanges no longer recreated on each puppet run if non-default vhost is used
- Allow port to be UNSET
- Re-added rabbitmq::server class
- Deprecated previously unused manage_service variable in favor of service_manage
- Use correct key for rabbitmq apt::source
- config_mirrored_queues variable removed
- It previously did nothing, will now at least throw a warning if you try to use it
- Remove unnecessary dependency on Class['rabbitmq::repo::rhel'] in rabbitmq::install
2013-09-14 - Version 3.1.0
Summary
This release focuses on a few small (but critical) bugfixes as well as extends the amount of custom RabbitMQ configuration you can do with the module.
Features
- You can now change RabbitMQ 'Config Variables' via the parameter
config_variables
. - You can now change RabbitMQ 'Environment Variables' via the parameter
environment_variables
. - ArchLinux support added.
Fixes
- Make use of the user/password parameters in rabbitmq_exchange{}
- Correct the read/write parameter order on set_permissions/list_permissions as they were reversed.
- Make the module pull down 3.1.5 by default.
2013-07-18 3.0.0
Summary
This release heavily refactors the RabbitMQ and changes functionality in several key ways. Please pay attention to the new README.md file for details of how to interact with the class now. Puppet 3 and RHEL are now fully supported. The default version of RabbitMQ has changed to a 3.x release.
Bugfixes
- Improve travis testing options.
- Stop reimporting the GPG key on every run on RHEL and Debian.
- Fix documentation to make it clear you don't have to set provider => each time.
- Reference the standard rabbitmq port in the documentation instead of a custom port.
- Fixes to the README formatting.
Features
- Refactor the module to fix RHEL support. All interaction with the module is now done through the main rabbitmq class.
- Add support for mirrored queues (Only on Debian family distributions currently)
- Add rabbitmq_exchange provider (using rabbitmqadmin)
- Add new
rabbitmq
class parameters:manage_service
: Boolean to choose if Puppet should manage the service. (For pacemaker/HA setups)
- Add SuSE support.
Incompatible Changes
- Rabbitmq::server has been removed and is now rabbitmq::config. You should not use this class directly, only via the main rabbitmq class.
2013-04-11 2.1.0
- remove puppetversion from rabbitmq.config template
- add cluster support
- escape resource names in regexp
2012-07-31 Jeff McCune jeff@puppetlabs.com 2.0.2
- Re-release 2.0.1 with $EDITOR droppings cleaned up
2012-05-03 2.0.0
- added support for new-style admin users
- added support for rabbitmq 2.7.1
2011-06-14 Dan Bode dan@Puppetlabs.com 2.0.0rc1
- Massive refactor:
- added native types for user/vhost/user_permissions
- added apt support for vendor packages
- added smoke tests
2011-04-08 Jeff McCune jeff@puppetlabs.com 1.0.4
- Update module for RabbitMQ 2.4.1 and rabbitmq-plugin-stomp package.
2011-03-24 1.0.3
- Initial release to the forge. Reviewed by Cody. Whitespace is good.
2011-03-22 1.0.2
- Whitespace only fix again... ack '\t' is my friend...
2011-03-22 1.0.1
- Whitespace only fix.
2011-03-22 1.0.0
- Initial Release. Manage the package, file and service.
Dependencies
- puppetlabs/stdlib (>=2.0.0 <5.0.0)
- puppetlabs/apt (>=1.0.0 <2.0.0)
- nanliu/staging (>=0.3.1 <2.0.0)
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2013 Puppet Labs 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.