1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
|
# Extlib module for Puppet
[](https://travis-ci.org/voxpupuli/puppet-extlib)
[](https://forge.puppetlabs.com/puppet/extlib)
[](https://forge.puppetlabs.com/puppet/extlib)
[](https://forge.puppetlabs.com/puppet/extlib)
[](https://forge.puppetlabs.com/puppet/extlib)
## Table of Contents
1. [Overview](#overview)
1. [Setup - The basics of getting started with extlib](#setup)
1. [Usage - Configuration options and additional functionality](#usage)
1. [Limitations - OS compatibility, etc.](#limitations)
1. [Development - Guide for contributing to the module](#development)
## Overview
This module provides functions and facts that are out of scope for [stdlib](https://github.com/puppetlabs/puppetlabs-stdlib).
Some of them are even intrinsically tied to stdlib.
## Setup
```console
% puppet module install puppet-extlib
```
## Usage
Since `puppet/extlib` version 3, all functions are provided under the `extlib` namespace.
Non namespaced versions were removed in version 5.
All functions are documented in [REFERENCE.md](REFERENCE.md)
### Facts
All facts in this module are namespaced and begin `extlib__`.
Facter 4 users can also find all facts under a single `extlib` toplevel
structured fact.
#### `extlib__puppet_config` (or `extlib['puppet_config']` when using facter 4)
A fact to expose puppet.conf settings. These are resolved on the agent, (unlike
`$settings::<setting_name>` which is resolved on the puppet master).
The following sections/settings are included.
```
{
main => {
hostpubkey,
hostprivkey,
hostcert,
localcacert,
ssldir,
vardir,
server,
},
master => {
localcacert,
ssldir,
}
}
```
## Limitations
Some functions require puppetlabs-stdlib (>= 4.6.0) and all functions are only
compatible with Puppet 4.7 and later.
## Development
We highly welcome new contributions to this module, especially those that
include documentation, and rspec tests ;) but will happily guide you through
the process, so, yes, please submit that pull request!
Reference documentation is generated using puppet-strings.
To regenerate it, please run the rake task as follows.
```console
bundle exec rake reference
```
|
