Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Server automation framework and application
Ruby HTML Shell Emacs Lisp VimL Makefile
Branch: master

(maint) Detect that a required resource is never exported

Addition to PUP-5083. A test that verifies that puppet detects if
a required resource is never exported. Prior to this it only tested
detection of lack of export for consumed resources.
latest commit 64a0cded8f
@thallgren thallgren authored
Failed to load latest commit information.
acceptance Merge pull request #4165 from er0ck/maint/master/remove_overloaded_gi…
api (PUP-4890) Add code_id accessor to the catalog
autotest (maint) Ensure every file has a trailing newlines
benchmarks (PUP-4702) Replace RGEN based Type system with immutable classes
bin (PUP-2563) Exit with 1 on pre-1.9.3 ruby
conf (PUP-4094) Update environment_timeout default in example environment.…
docs Merge pull request #3709 from kylog/docs/spec-order
examples/hiera (Maint) Update commands to use new forms in hiera examples
ext Merge remote-tracking branch 'origin/stable'
lib Merge remote-tracking branch 'upstream/stable'
man (docs) Generate man pages
spec (maint) Detect that a required resource is never exported
tasks (PUP-3912) Add legacy_formatters gem for junit integration
util (PUP-3912) Update parallel:spec task for rspec 3
yardoc/templates/default (#18023) Document user facing classes using yardoc and show api.
.gemspec (maint) Update gemspec to assume at least the rubygems version includ…
.gitignore (PUP-4347) Add test for the File resource ignore attribute
.mailmap (maint) Update mailmap for git shortlog
.noexec.yaml (#15464) Exclude gem command from bundler
.rubocop.yml (maint) Enable rubocop checking for shadowed variables
.travis.yml (maint) Remove redundant travis jobs
.yardopts (maint) Remove reference to README_DEVELOPER (maint) Clarify the merge-up process in COMMITTERS (maint) Fix typo in
Gemfile Merge pull request #3741 from ffrank/maint/cleaner-http-stubbing
LICENSE (maint) Update copyright years in LICENSE (doc) 'JIRA tracker' link fix in the README
Rakefile (maint) Update commit rake task to allow revert
appveyor.yml (maint) remove extra gems from appveyor
install.rb (PUP-5051) Add --no-check-prereqs flag to install.rb


Build Status 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 for Puppet and related projects can be found online at the Puppet Docs site.




The best way to run Puppet is with Puppet Enterprise, 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 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 you can take a look at the rest of the developer documents.


See LICENSE file.


Please log tickets and issues at our JIRA tracker. A mailing list is available for asking questions and getting help from others. In addition there is an active #puppet channel on Freenode.

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.

Bugfixes 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 4.1.1, we would fix it in the 4 series, most likely as 4.1.2. Maintainers would then make a best effort to backport that fix onto the latest Puppet 3 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

Something went wrong with that request. Please try again.