├── .gitignore ├── CODEOWNERS ├── data ├── nodes │ └── example-node.yaml └── common.yaml ├── site-modules ├── adhoc │ ├── tasks │ │ ├── win_example.ps1 │ │ ├── nix_example.sh │ │ ├── nix_example.json │ │ └── win_example.json │ └── plans │ │ └── myplan.pp ├── role │ └── manifests │ │ ├── example.pp │ │ ├── webserver.pp │ │ └── database_server.pp └── profile │ └── manifests │ ├── example.pp │ └── base.pp ├── environment.conf ├── hiera.yaml ├── Puppetfile ├── scripts ├── config_version-r10k.rb ├── config_version-rugged.rb └── config_version.sh ├── manifests └── site.pp ├── README.md └── LICENSE /.gitignore: -------------------------------------------------------------------------------- 1 | modules/ 2 | -------------------------------------------------------------------------------- /CODEOWNERS: -------------------------------------------------------------------------------- 1 | * @puppetlabs/cs-arch 2 | -------------------------------------------------------------------------------- /data/nodes/example-node.yaml: -------------------------------------------------------------------------------- 1 | --- 2 | -------------------------------------------------------------------------------- /data/common.yaml: -------------------------------------------------------------------------------- 1 | --- 2 | message: "This node is using common data" 3 | -------------------------------------------------------------------------------- /site-modules/adhoc/tasks/win_example.ps1: -------------------------------------------------------------------------------- 1 | # task content goes here 2 | -------------------------------------------------------------------------------- /site-modules/adhoc/tasks/nix_example.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # task content goes here 4 | -------------------------------------------------------------------------------- /site-modules/role/manifests/example.pp: -------------------------------------------------------------------------------- 1 | # An example role 2 | class role::example { 3 | 4 | } 5 | -------------------------------------------------------------------------------- /site-modules/profile/manifests/example.pp: -------------------------------------------------------------------------------- 1 | # An example profile 2 | class profile::example { 3 | 4 | } 5 | -------------------------------------------------------------------------------- /environment.conf: -------------------------------------------------------------------------------- 1 | modulepath = site-modules:modules:$basemodulepath 2 | config_version = 'scripts/config_version.sh $environmentpath $environment' 3 | -------------------------------------------------------------------------------- /site-modules/profile/manifests/base.pp: -------------------------------------------------------------------------------- 1 | # The base profile should include component modules that will be on all nodes 2 | class profile::base { 3 | 4 | } 5 | -------------------------------------------------------------------------------- /site-modules/adhoc/tasks/nix_example.json: -------------------------------------------------------------------------------- 1 | { 2 | "description": "This is the description for the nix_example task", 3 | "input_method": "environment" 4 | } 5 | -------------------------------------------------------------------------------- /site-modules/adhoc/tasks/win_example.json: -------------------------------------------------------------------------------- 1 | { 2 | "description": "This is the description for the win_example task", 3 | "input_method": "powershell" 4 | } 5 | -------------------------------------------------------------------------------- /site-modules/adhoc/plans/myplan.pp: -------------------------------------------------------------------------------- 1 | # This is a description for my plan 2 | plan adhoc::myplan( 3 | # input parameters go here 4 | TargetSpec $targets, 5 | ) { 6 | 7 | # plan steps go here 8 | 9 | } 10 | -------------------------------------------------------------------------------- /hiera.yaml: -------------------------------------------------------------------------------- 1 | --- 2 | version: 5 3 | 4 | defaults: 5 | datadir: "data" 6 | 7 | hierarchy: 8 | - name: "Yaml backend" 9 | data_hash: yaml_data 10 | paths: 11 | - "nodes/%{trusted.certname}.yaml" 12 | - "common.yaml" 13 | -------------------------------------------------------------------------------- /site-modules/role/manifests/webserver.pp: -------------------------------------------------------------------------------- 1 | # This role would be made of all the profiles that need to be included to make a webserver work 2 | # All roles should include the base profile 3 | class role::webserver { 4 | 5 | include profile::base 6 | 7 | } 8 | -------------------------------------------------------------------------------- /site-modules/role/manifests/database_server.pp: -------------------------------------------------------------------------------- 1 | # This role would be made of all the profiles that need to be included to make a database server work 2 | # All roles should include the base profile 3 | class role::database_server { 4 | 5 | include profile::base 6 | 7 | } 8 | -------------------------------------------------------------------------------- /Puppetfile: -------------------------------------------------------------------------------- 1 | forge 'https://forge.puppet.com' 2 | 3 | # Modules from the Puppet Forge 4 | # Versions should be updated to be the latest at the time you start 5 | #mod 'puppetlabs/inifile', '5.0.1' 6 | #mod 'puppetlabs/stdlib', '7.0.1' 7 | #mod 'puppetlabs/concat', '7.0.1' 8 | 9 | # Modules from Git 10 | # Examples: https://github.com/puppetlabs/r10k/blob/master/doc/puppetfile.mkd#examples 11 | #mod 'apache', 12 | # git: 'https://github.com/puppetlabs/puppetlabs-apache', 13 | # commit: '1b6f89afdde0df7f9433a163d5c4b5328eac5779' 14 | 15 | #mod 'apache', 16 | # git: 'https://github.com/puppetlabs/puppetlabs-apache', 17 | # branch: 'docs_experiment' 18 | -------------------------------------------------------------------------------- /scripts/config_version-r10k.rb: -------------------------------------------------------------------------------- 1 | #!/opt/puppetlabs/puppet/bin/ruby 2 | require 'json' 3 | require 'socket' 4 | 5 | environmentpath = ARGV[0] 6 | environment = ARGV[1] 7 | 8 | # Get the hostname of the Puppet master compiling the catalog. 9 | # Sometimes the hostname is the fqdn, so we'll take the first segment. 10 | compiling_master = Socket.gethostname.split('.').first 11 | 12 | # Get the path to the Code Manager deployment info file. 13 | r10k_deploy_file_path = File.join(environmentpath, environment, '.r10k-deploy.json') 14 | 15 | # Get the first 12 characters of the commit ID out of the deployment file. 16 | commit_id = JSON.parse(File.read(r10k_deploy_file_path))['signature'][0...11] 17 | 18 | # Show the compiling master, environment name, and commit ID. 19 | puts "#{compiling_master}-#{environment}-#{commit_id}" 20 | -------------------------------------------------------------------------------- /scripts/config_version-rugged.rb: -------------------------------------------------------------------------------- 1 | #!/opt/puppetlabs/puppet/bin/ruby 2 | begin 3 | require 'rugged' 4 | require 'socket' 5 | rescue LoadError 6 | t = Time.new 7 | puts t.to_i 8 | else 9 | environmentpath = ARGV[0] 10 | environment = ARGV[1] 11 | 12 | # Get the hostname of the Puppet master compiling the catalog. 13 | # Sometimes the hostname is the fqdn, so we'll take the first segment. 14 | compiling_master = Socket.gethostname.split('.').first 15 | 16 | # Get the path to the environment being compiled. 17 | repo = Rugged::Repository.discover(File.join(environmentpath, environment)) 18 | head = repo.head 19 | 20 | # First 12 characters of the sha1 hash of the newest commit. 21 | commit_id = head.target_id[0...11] 22 | 23 | # Show the compiling master, environment name, and commit ID. 24 | puts "#{compiling_master}-#{environment}-#{commit_id}" 25 | end 26 | -------------------------------------------------------------------------------- /scripts/config_version.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | # Usage 4 | if [ $# -ne 2 -o ! -d "$1" -o ! -d "$1/$2" ]; then 5 | echo "usage: $0 " >&2 6 | exit 1 7 | fi 8 | 9 | # For portability, identify a preferred ruby executable to use 10 | ruby() { 11 | [ -x /opt/puppetlabs/puppet/bin/ruby ] \ 12 | && /opt/puppetlabs/puppet/bin/ruby "$@" \ 13 | || /usr/bin/env ruby "$@" 14 | } 15 | 16 | # Determine how best to calculate a config_version 17 | if [ -e $1/$2/.r10k-deploy.json ]; then 18 | # The environment was deployed using r10k. We will calculate the config 19 | # version using the r10k data. 20 | ruby $1/$2/scripts/config_version-r10k.rb $1 $2 21 | 22 | elif [ -e /opt/puppetlabs/server/pe_version ]; then 23 | # This is a Puppet Enterprise system and we can rely on the rugged ruby gem 24 | # being available. 25 | ruby $1/$2/scripts/config_version-rugged.rb $1 $2 26 | 27 | elif type git >/dev/null && [ -d "$1/$2/.git" ]; then 28 | # The git command is available. 29 | git --git-dir $1/$2/.git rev-parse HEAD 30 | 31 | else 32 | # Nothing else available; just use the date. 33 | date +%s 34 | 35 | fi 36 | -------------------------------------------------------------------------------- /manifests/site.pp: -------------------------------------------------------------------------------- 1 | ## site.pp ## 2 | 3 | # This file (./manifests/site.pp) is the main entry point 4 | # used when an agent connects to a master and asks for an updated configuration. 5 | # https://puppet.com/docs/puppet/latest/dirs_manifest.html 6 | # 7 | # Global objects like filebuckets and resource defaults should go in this file, 8 | # as should the default node definition if you want to use it. 9 | 10 | ## Active Configurations ## 11 | 12 | # Disable filebucket by default for all File resources: 13 | # https://github.com/puppetlabs/docs-archive/blob/master/pe/2015.3/release_notes.markdown#filebucket-resource-no-longer-created-by-default 14 | File { backup => false } 15 | 16 | ## Node Definitions ## 17 | 18 | # The default node definition matches any node lacking a more specific node 19 | # definition. If there are no other node definitions in this file, classes 20 | # and resources declared in the default node definition will be included in 21 | # every node's catalog. 22 | # 23 | # Note that node definitions in this file are merged with node data from the 24 | # Puppet Enterprise console and External Node Classifiers (ENC's). 25 | # 26 | # For more on node definitions, see: https://puppet.com/docs/puppet/latest/lang_node_definitions.html 27 | node default { 28 | # This is where you can declare classes for all nodes. 29 | # Example: 30 | # class { 'my_class': } 31 | } 32 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # A Puppet Control Repository 2 | 3 | * [What You Get From This control\-repo](#what-you-get-from-this-control-repo) 4 | * [Copy This Repo Into Your Own Git Server](#copy-this-repo-into-your-own-git-server) 5 | * [GitLab](#gitlab) 6 | * [Bitbucket/Stash](#bitbucketstash) 7 | * [Github](#github) 8 | * [Code Manager Setup](#code-manager-setup) 9 | 10 | 11 | ## What You Get From This control-repo 12 | 13 | This is a template [control repository](https://puppet.com/docs/pe/latest/control_repo.html) that has the minimum amount of scaffolding to make it easy to get started with [r10k](https://puppet.com/docs/pe/latest/r10k.html) or Puppet Enterprise's [Code Manager](https://puppet.com/docs/pe/latest/code_mgr.html). 14 | 15 | The important files and items in this template are as follows: 16 | 17 | * Basic example of roles and profiles. 18 | * An example Puppetfile with various module references. 19 | * An example Hiera configuration file and data directory with pre-created common.yaml and nodes directory. 20 | * These match the default hierarchy that ships with PE. 21 | * An [environment.conf](https://puppet.com/docs/puppet/7/config_file_environment.html) that correctly implements: 22 | * A site-modules directory for roles, profiles, and any custom modules for your organization. 23 | * A config\_version script. 24 | * An example [config\_version](https://puppet.com/docs/puppet/7/config_file_environment.html#environment-conf-allowed-settings) script that outputs the git commit ID of the code that was used during a Puppet run. 25 | 26 | Here's a visual representation of the structure of this repository: 27 | 28 | ``` 29 | control-repo/ 30 | ├── data/ # Hiera data directory. 31 | │   ├── nodes/ # Node-specific data goes here. 32 | │   └── common.yaml # Common data goes here. 33 | ├── manifests/ 34 | │   └── site.pp # The "main" manifest that contains a default node definition. 35 | ├── scripts/ 36 | │   ├── code_manager_config_version.rb # A config_version script for Code Manager. 37 | │   ├── config_version.rb # A config_version script for r10k. 38 | │   └── config_version.sh # A wrapper that chooses the appropriate config_version script. 39 | ├── site-modules/ # This directory contains site-specific modules and is added to $modulepath. 40 | │   ├── profile/ # The profile module. 41 | │   └── role/ # The role module. 42 | ├── LICENSE 43 | ├── Puppetfile # A list of external Puppet modules to deploy with an environment. 44 | ├── README.md 45 | ├── environment.conf # Environment-specific settings. Configures the modulepath and config_version. 46 | └── hiera.yaml # Hiera's configuration file. The Hiera hierarchy is defined here. 47 | ``` 48 | 49 | ## Copy This Repo Into Your Own Git Server 50 | 51 | To get started with using the control-repo template in your own environment and git server, we've provided steps for the three most common servers we see: [GitLab](#gitlab), [BitBucket](#bitbucketstash), and [GitHub](#github). 52 | 53 | ### GitLab 54 | 55 | 1. Install GitLab. 56 | * 57 | 1. After GitLab is installed you may sign in with the `root` user. If you didn't specify a custom password during installation, a temporary password is located in `/etc/gitlab/initial_root_password`. 58 | 1. Make a user for yourself. 59 | 1. Make an SSH key to link with your user. You’ll want to do this on the machine you intend to edit code from (most likely not your Puppet master, but your local workstation or laptop). 60 | * 61 | * 62 | 1. Create a group called `puppet` (this is case sensitive). 63 | * 64 | 1. Add your user to the `puppet` group as well. 65 | 1. Create a project called `control-repo`, and set the Namespace to be the `puppet` group. 66 | 1. Clone this control repository to your laptop/workstation: 67 | * `git clone ` 68 | * `cd control-repo` 69 | 1. Remove this repository as the origin remote: 70 | * `git remote remove origin` 71 | 1. Add your internal repository as the origin remote: 72 | * `git remote add origin ` 73 | 1. Push the production branch of the repository from your machine up to your git server 74 | * `git push origin production` 75 | 76 | ### Bitbucket/Stash 77 | 78 | 1. Install Bitbucket 79 | * 80 | 1. Make a `Project` called `puppet` (with a short name of `PUP`) 81 | 1. Create a repository called `control-repo` 82 | 1. Create a user called `r10k` with a password of `puppet`. 83 | * Make the r10k user an admin of the `PUP` project. 84 | 1. Either use the admin user to test pushing code, or create a user for yourself and add your SSH key to that user. 85 | * If making a user for yourself, give your user account read/write or admin privilege to the `PUP` project. 86 | 1. Clone this control repository to your laptop/workstation 87 | * `git clone ` 88 | * `cd control-repo` 89 | 1. Remove this repository as the origin remote 90 | * `git remote remove origin` 91 | 1. Add your internal repository as the origin remote 92 | * `git remote add origin ` 93 | 1. Push the production branch of the repository from your machine up to your git server 94 | * `git push origin production` 95 | 96 | ### GitHub 97 | 98 | Follow [GitHub's documentation](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template) to create your control repository starting from this template. 99 | 100 | template button 101 | 102 | 103 | ### GitHub Enterprise 104 | 105 | 1. Prepare your local git client to authenticate with a **local GitHub Enterprise instance**. 106 | * 107 | * 108 | 1. Create a repository called `control-repo` in your user account or organization. Ensure that "Initialize this repository with a README" is not selected. 109 | * 110 | 1. Make a note of your repository URL (HTTPS or SSH, depending on your security configuration). 111 | 1. Clone this control repository to your laptop/workstation: 112 | * `git clone ` 113 | * `cd control-repo` 114 | 1. Remove this repository as the origin remote: 115 | * `git remote remove origin` 116 | 1. Add your internal repository as the origin remote: 117 | * `git remote add origin ` 118 | 1. Push the production branch of the repository from your machine up to your git server 119 | * `git push origin production` 120 | 121 | ## Code Manager Setup 122 | 123 | If you use Puppet Enterprise see the official [documentation](https://puppet.com/docs/pe/latest/code_mgr.html) for enabling Code Manager. 124 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "{}" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright {yyyy} {name of copyright owner} 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | 203 | --------------------------------------------------------------------------------