Skip to content
Server automation framework and application
Ruby HTML Shell Puppet C# Makefile
Branch: master
Clone or download

Latest commit

Latest commit adcdbfb Apr 28, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
acceptance (PUP-10299) Add SemVerRange support to zypper (#8095) Apr 28, 2020
api (docs) update ca v1 http api section Jan 10, 2019
benchmarks (maint) Merge up e4a5940 to master Jan 25, 2020
bin (PUP-3478) Remove extlookup2hiera Apr 19, 2017
conf (docs) Update URLs in config files. May 9, 2018
docs (maint) Add flow chart for http client ca service Jan 23, 2020
examples/hiera (Maint) Update commands to use new forms in hiera examples Sep 19, 2013
ext (PUP-10414) Fix option parsing when running with debug Apr 15, 2020
lib Merge pull request #8118 from joshcooper/merge_55x_master Apr 28, 2020
locales (packaging) Updating the puppet.pot file Apr 25, 2020
man (packaging) Updating manpage file for master Apr 27, 2020
spec Merge pull request #8118 from joshcooper/merge_55x_master Apr 28, 2020
tasks (PUP-10365) Create separate test fixture CA hierarchy Mar 17, 2020
util (maint) Enable Lint/DeprecatedClassMethods Oct 9, 2019
yardoc/templates/default (#18023) Document user facing classes using yardoc and show api. Jan 5, 2013
.gemspec (packaging) Bump to version '6.16.0' [no-promote] Apr 27, 2020
.gitignore (maint) Add `spec_order.txt` to .gitignore Feb 11, 2020
.gitmodules (maint) Add full catalog benchmark Mar 9, 2018
.hound.yml (maint) Point HoundCI at the existing rubocop config Mar 24, 2016
.mailmap (maint) Update mailmap for git shortlog Oct 18, 2012
.noexec.yaml (#15464) Exclude gem command from bundler Aug 20, 2012
.rubocop.yml (maint) Remove stale rubocop exclusions Oct 9, 2019
.travis.yml (maint) Bump to JRuby 9.2.8.0 in Travis Feb 10, 2020
.yardopts (doc) Prevent Yard from documenting vendor code. Aug 23, 2016
CODEOWNERS (maint) Fix CODEOWNERS so we don't override platform-core Jan 4, 2020
CODE_OF_CONDUCT.md (maint) Create CODE_OF_CONDUCT.md Feb 14, 2019
CONTRIBUTING.md (maint) Update CONTRIBUTING.md Mar 3, 2020
Gemfile (PUP-10091) Add FacterNg dependency Dec 2, 2019
Guardfile.example (maint) Add example Guardfile Nov 1, 2018
LICENSE (docs) edit Puppet license info so that GitHub recognizes it Jun 28, 2018
README.md (maint) Update CONTRIBUTING.md Mar 3, 2020
Rakefile Merge remote-tracking branch 'upstream/5.5.x' into 6.0.x Dec 13, 2018
appveyor.yml (maint) Drop ruby 24 & 25 with ja_JP from appveyor Nov 8, 2019
install.rb (maint) Resolve ruby -wc warnings Oct 9, 2019

README.md

Puppet

Travis Status Appveyor Status Gem Version Inline docs

Puppet, an automated administrative engine for your Linux, Unix, and Windows systems, performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.

Documentation

Documentation for Puppet and related projects can be found online at the Puppet Docs site.

HTTP API

HTTP API Index

Installation

The best way to run Puppet is with Puppet Enterprise (PE), which also includes orchestration features, a web console, and professional support. The PE documentation is available here.

To install an open source release of Puppet, see the installation guide on the docs site.

If you need to run Puppet from source as a tester or developer, see the Running Puppet from Source guide on the docs site.

Developing and Contributing

We'd love to get contributions from you! For a quick guide to getting your system setup for developing, take a look at our Quickstart Guide. Once you are up and running, take a look at the Contribution Documents to see how to get your changes merged in.

For more complete docs on developing with Puppet, take a look at the rest of the developer documents.

Licensing

See LICENSE file. Puppet is licensed by Puppet, Inc. under the Apache license. Puppet, Inc. can be contacted at: info@puppet.com

Support

Please log tickets and issues at our JIRA tracker. A mailing list is available for asking questions and getting help from others, or if you prefer chat, we also have a Puppet Community slack.

We use semantic version numbers for our releases and recommend that users stay as up-to-date as possible by upgrading to patch releases and minor releases as they become available.

Bug fixes and ongoing development will occur in minor releases for the current major version. Security fixes will be backported to a previous major version on a best-effort basis, until the previous major version is no longer maintained.

For example: If a security vulnerability is discovered in Puppet 6.1.1, we would fix it in the 6 series, most likely as 6.1.2. Maintainers would then make a best effort to backport that fix onto the latest Puppet 5 release.

Long-term support, including security patches and bug fixes, is available for commercial customers. Please see the following page for more details:

Puppet Enterprise Support Lifecycle

You can’t perform that action at this time.