Skip to content
Confine Puppet providers based on libs (Gems)
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib/puppet/confine
spec
.gitignore
.travis.yml
Gemfile
LICENSE
README.md
Rakefile
metadata.json

README.md

Puppet confinelibs Module

Build Status

Table of Contents

  1. Overview
  2. Description
  3. Usage
  4. Limitations
  5. Versioning
  6. Support
  7. Contributing
  8. See Also

Overview

Confine Puppet providers based on libs (Gems)

Description

Create a Puppet::Confine instance that requires a list of libs (Gems). A separate Puppet::Util::Feature is created for each lib. This is similar to Puppet::Confine::Feature for lib dependencies except that a feature does not need to be manually declared.

Usage

Examples

Single lib

confine :libs => "simple-graphite"

Ruby 1.9+ JSON style

confine libs: "simple-graphite"

Multiple libs

confine :libs => ["openstack", "slackcat"]

Equivalent to:

confine :libs => "openstack"
confine :libs => "slackcat"

Equivalent to:

confine :libs => ["openstack"]
confine :libs => ["slackcat"]

Ruby 1.9+ JSON style

confine libs: ["openstack", "slackcat"]

Limitations

Tested Puppets

  • 3.7.5
  • 4.0.0

Versioning

This module is versioned according to the Semantic Versioning 2.0.0 specification.

Support

Please log tickets and issues at github

Contributing

  1. Fork it on github
  2. Make a local clone of your fork
  3. Create a topic branch. Eg, feature/mousetrap
  4. Make/commit changes
    • Commit messages should be in imperative tense
    • Check that linter warnings or errors are not introduced - bundle exec rake lint
    • Check that Rspec-puppet unit tests are not broken and coverage is added for new features - bundle exec rake spec
    • Documentation of API/features is updated as appropriate in the README
    • If present, beaker acceptance tests should be run and potentially updated - bundle exec rake beaker
  5. When the feature is complete, rebase / squash the branch history as necessary to remove "fix typo", "oops", "whitespace" and other trivial commits
  6. Push the topic branch to github
  7. Open a Pull Request (PR) from the topic branch onto parent repo's master branch

See Also

You can’t perform that action at this time.