Version information
This version is compatible with:
- Puppet Enterprise 2023.8.x, 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
- Puppet >= 4.0.0
- , , , , , ,
Start using this module
Add this module to your Puppetfile:
mod 'eyp-puppet', '0.3.2'
Learn more about managing modules with a PuppetfileDocumentation
puppet
Table of Contents
- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with puppet
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Development - Guide for contributing to the module
Overview
puppet client management
Module Description
If applicable, this section should have a brief description of the technology the module integrates with and what that integration enables. This section should answer the questions: "What does this module do?" and "Why would I use it?"
If your module has a range of functionality (installation, configuration, management, etc.) this is the time to mention it.
Setup
What puppet affects
- A list of files, packages, services, or operations that the module will alter, impact, or execute on the system it's installed on.
- This is a great place to stick any warnings.
- Can be in list or paragraph form.
Beginning with puppet
class { 'puppet::agent':
puppetmaster => 'demoserver',
puppetmasterport => '1234',
puppetenv => 'tstenv',
}
Usage
Put the classes, types, and resources for customizing, configuring, and doing the fancy stuff with your module here.
Reference
Here, list the classes, types, providers, facts, etc contained in your module. This section should include all of the under-the-hood workings of your module so people know what the module is touching on their system but don't need to mess with things. (We are working on automating this section!)
Development
We are pushing to have acceptance testing in place, so any new feature should have some tests to check both presence and absence of any feature
TODO
- improve configuration options
Contributing
- Fork it
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Added some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create new Pull Request
CHANGELOG
0.3.2
- added runinterval setting for puppet::agent
0.3.1
- bugfix
0.3.0
- environment variable for puppet agent
0.2.3
- added support for SLES11SP4
0.2.2
- added support for SLES11SP3
0.2.1
- added option to disable management of puppet agent's configuration
0.2.0
- updated to puppet 5
- Added SLES12SP3 support
- puppet::client renamed to puppet::agent
- added puppet::client compatibility class that translats variables to puppet::agent
0.1.27
- added Ubuntu 18.04 support
0.1.26
- improved nagios check: check_last_puppet_run and moved to the files directory
0.1.25
- added service_enable varible to puppet::client
0.1.24
- Ubuntu 16.04 support
0.1.23
- bugfix check_last_puppet_run
0.1.22
- added check_last_puppet_run
Dependencies
- puppetlabs/stdlib (>= 4.6.0 < 9.9.9)
- puppetlabs/concat (>= 1.2.3 < 9.9.9)
- eyp/eyplib (>= 0.1.16 < 0.2.0)