Forge Home

facter

Manage Facter

85,777 downloads

2,527 latest version

3.1 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 4.0.0 (latest)
  • 3.5.0
  • 3.4.0
  • 3.3.1
  • 3.3.0
  • 3.2.0
  • 3.1.0
  • 3.0.0
  • 2.1.0
  • 2.0.1
  • 1.3.2
  • 1.3.1
  • 1.3.0
  • 1.2.1
  • 1.2.0
  • 1.1.2
  • 1.0.0 (deleted)
released Jul 23rd 2015
This version is compatible with:
  • Puppet Enterprise 3.x
  • Puppet 3.x
  • AIX, Debian, RedHat, CentOS, OracleLinux, Scientific, Solaris, SLES, SLED, Ubuntu

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'ghoneycutt-facter', '2.0.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add ghoneycutt-facter
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install ghoneycutt-facter --version 2.0.1

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download
Tags: puppet, facter

Documentation

ghoneycutt/facter — version 2.0.1 Jul 23rd 2015

puppet-module-facter

===

Build Status

Puppet module to manage Facter

===

Compatibility


This module is built for use with Puppet v3 and supports Ruby v1.8.7, v1.9.3, v2.0.0 and v2.1.0.

===

Parameters


manage_package

Boolean to manage the package resource.

  • Default: true

package_name

String or Array of package(s) for facter.

  • Default: 'facter'

package_ensure

String for ensure parameter to facter package.

  • Default: present

manage_facts_d_dir

Boolean to manage the directory.

  • Default: true

facts_d_dir

Path to facts.d directory.

  • Default: /etc/facter/facts.d

facts_d_owner

Owner of facts.d directory.

  • Default: root

facts_d_group

Group of facts.d directory.

  • Default: root

facts_d_mode

Four digit mode of facts.d directory.

  • Default: 0755

path_to_facter

Path to facter to create symlink from. Required if ensure_facter_symlink is true.

  • Default: '/usr/bin/facter'

path_to_facter_symlink

Path to symlink for facter. Required if ensure_facter_symlink is true.

  • Default: '/usr/local/bin/facter'

ensure_facter_symlink

Boolean for ensuring a symlink for path_to_facter to symlink_facter_target. This is useful if you install facter in a non-standard location that is not in your $PATH.

  • Default: false

facts_hash

Hash of facts to be passed to facter::fact with create_resources().

  • Default: undef

facts_file

Filename under facts_d_dir to place facts in

  • Default: facts.txt

facts_file_owner

Owner of facts_file.

  • Default: root

facts_d_group

Group of facst_file.

  • Default: root

facts_d_mode

Four digit mode of facts_file.

  • Default: 0644

===

Define facter::fact

Ensures a fact is present in the fact file with stdlib file_line() in fact=value format.

Usage

You can optionally specify a hash of external facts in Hiera.

facter::facts: role: value: 'puppetmaster' location: value: 'RNB' file: 'location.txt'

The above configuration in Hiera would produce /etc/facter/facts.d/facts.txt with the following content.

It would also produce /etc/facter/facts.d/location.txt with the following content.

value

Value for the fact

  • Required

fact

Name of the fact

  • Default: $name

file

File under facts_dir in which to place the fact.

  • Default: 'facts.txt'

facts_dir

Path to facts.d directory.

  • Default: '/etc/facter/facts.d'