A typical fact in Facter is an collection of several elements, and is written either as a simple value (“flat” fact) or as structured data (“structured” fact).
This page is an example-driven tour of those elements, and is a quick primer or reference for people writing custom facts. You need some familiarity with Ruby to understand most of these examples. For a gentler introduction, check out the Custom facts walkthrough.
It’s important to distinguish between facts and resolutions. A fact is a piece of information about a given node, while a resolution is a way of obtaining that information from the system. Every fact must have at least one resolution, and facts that can run on different operating systems could have different resolutions for each OS.
Although facts and resolutions are conceptually very different, the line can get a bit blurry at times, because declaring a second (or more) resolution for a fact looks just like declaring a completely new fact, with the same name as an existing fact.
For information on how to add custom facts to modules, see Module plug-in types.
Writing facts with simple resolutions
Most facts are resolved all at the same time, without any need to merge data from different sources. In that case, the resolution is simple. Both flat and structured facts can have simple resolutions.
Example: Minimal fact that relies on a single shell command
Facter.add(:rubypath) do
setcode 'which ruby'
end
Example: Different resolutions for different operating systems
Facter.add(:rubypath) do
setcode 'which ruby'
end
Facter.add(:rubypath) do
confine :osfamily => "Windows"
# Windows uses 'where' instead of 'which'
setcode 'where ruby'
end
Example: Slightly more complex fact, confined to Linux with a block
Facter.add(:jruby_installed) do
confine :kernel do |value|
value == "Linux"
end
setcode do
# If jruby is present, return true. Otherwise, return false.
Facter::Core::Execution.which('jruby') != nil
end
end
Main components of simple resolutions
-
A call to
Facter.add(:fact_name)
:- This introduces a new fact or a new resolution for an existing fact with the same name.
-
The name can be either a symbol or a string.
-
The rest of the fact is wrapped in the
add
call’sdo ... end
block.
-
Zero or more
confine
statements:-
Determine whether the resolution is suitable (and therefore is evaluated).
-
Can either match against the value of another fact or evaluate a Ruby block.
-
If given a symbol or string representing a fact name, a block is required and the block receives the fact’s value as an argument.
-
If given a hash, the keys are expected to be fact names. The values of the hash are either the expected fact values or an array of values to compare against.
-
If given a block, the confine is suitable if the block returns a value other than
nil
orfalse
.
-
-
An optional
has_weight
statement:-
When multiple resolutions are available for a fact, resolutions are evaluated from highest weight value to lowest.
-
Must be an integer greater than 0.
-
Defaults to the number of
confine
statements for the resolution.
-
-
A
setcode
statement that determines the value of the fact:-
Can take either a string or a block.
-
If given a string, Facter executes it as a shell command. If the command succeeds, the output of the command is the value of the fact. If the command fails, the next suitable resolution is evaluated.
-
If given a block, the block’s return value is the value of the fact unless the block returns
nil
. Ifnil
is returned, the next suitable resolution is evalutated. -
Can execute shell commands within a
setcode
block, using theFacter::Core::Execution.exec
function. -
If multiple
setcode
statements are evaluated for a single resolution, only the lastsetcode
block is used.
Note: Set all code inside the sections outlined above — there should not be any code outsidesetcode
andconfine
blocks other than an optionalhas_weight
statement in a custom fact. -
Writing structured facts
Structured facts can take the form of hashes or arrays.
You don’t have to do anything special to mark the fact as structured — if your fact returns a hash or array, Facter recognizes it as a structured fact. Structured facts can have simple or aggregate resolutions.
Example: Returning an array of network interfaces
Facter.add(:interfaces_array) do
setcode do
interfaces = Facter.value(:interfaces)
# the 'interfaces' fact returns a single comma-delimited string, such as "lo0,eth0,eth1"
# this splits the value into an array of interface names
interfaces.split(',')
end
end
Example: Returning a hash of network interfaces to IP addresses
Facter.add(:interfaces_hash) do
setcode do
interfaces_hash = {}
Facter.value(:interfaces_array).each do |interface|
ipaddress = Facter.value("ipaddress_#{interface}")
if ipaddress
interfaces_hash[interface] = ipaddress
end
end
interfaces_hash
end
end
Writing facts with aggregate resolutions
Aggregate resolutions allow you to split up the resolution of a fact into separate chunks.
By default, Facter merges hashes with hashes or arrays with arrays, resulting in a structured fact, but you can also aggregate the chunks into a flat fact using concatenation, addition, or any other function that you can express in Ruby code.
Main components of aggregate resolutions
Aggregate resolutions have two key differences compared to simple resolutions: the presence of chunk
statements and the lack of a setcode
statement. The aggregate
block is optional, and without it Facter merges hashes with hashes or arrays with arrays.
A call to
Facter.add(:fact_name, :type => :aggregate)
:Introduces a new fact or a new resolution for an existing fact with the same name.
The name can be either a symbol or a string.
The
:type => :aggregate
parameter is required for aggregate resolutions.The rest of the fact is wrapped in the
add
call’sdo ... end
block.
Zero or more
confine
statements:Determine whether the resolution is suitable and (therefore is evaluated).
They can either match against the value of another fact or evaluate a Ruby block.
If given a symbol or string representing a fact name, a block is required and the block receives the fact’s value as an argument.
If given a hash, the keys are expected to be fact names. The values of the hash are either the expected fact values or an array of values to compare against.
If given a block, the confine is suitable if the block returns a value other than
nil
orfalse
.
An optional
has_weight
statement:Evaluates multiple resolutions for a fact from highest weight value to lowest.
Must be an integer greater than 0.
Defaults to the number of
confine
statements for the resolution.
One or more calls to
chunk
, each containing:A name (as the argument to
chunk
).A block of code, which is responsible for resolving the chunk to a value. The block’s return value is the value of the chunk; it can be any type, but is typically a hash or array.
An optional
aggregate
block:If absent, Facter automatically merges hashes with hashes or arrays with arrays.
To merge the chunks in any other way, you need to make a call to
aggregate
, which takes a block of code.The block is passed one argument (
chunks
, in the example), which is a hash of chunk name to chunk value for all the chunks in the resolution.
Example: Building a structured fact progressively
networking_primary_sha
, by progressively merging two chunks. One chunk encodes each networking interface’s MAC address as an encoded base64 value, and the other determines if each interface is the system’s primary interface. require 'digest'
require 'base64'
Facter.add(:networking_primary_sha, :type => :aggregate) do
chunk(:sha256) do
interfaces = {}
Facter.value(:networking)['interfaces'].each do |interface, values|
if values['mac']
hash = Digest::SHA256.digest(values['mac'])
encoded = Base64.encode64(hash)
interfaces[interface] = {:mac_sha256 => encoded.strip}
end
end
interfaces
end
chunk(:primary?) do
interfaces = {}
Facter.value(:networking)['interfaces'].each do |interface, values|
interfaces[interface] = {:primary? => (interface == Facter.value(:networking)['primary'])}
end
interfaces
end
# Facter merges the return values for the two chunks
# automatically, so there's no aggregate statement.
end
The fact’s output is organized by network interface into hashes, each containing the two chunks:{
bridge0 => {
mac_sha256 => "bfgEFV7m1V04HYU6UqzoNoVmnPIEKWRSUOU650j0Wkk=",
primary? => false
},
en0 => {
mac_sha256 => "6Fd3Ws2z+aIl8vNmClCbzxiO2TddyFBChMlIU+QB28c=",
primary? => true
},
...
}
Example: Building a flat fact progressively with addition
Facter.add(:total_free_memory_mb, :type => :aggregate) do
chunk(:physical_memory) do
Facter.value(:memoryfree_mb)
end
chunk(:virtual_memory) do
Facter.value(:swapfree_mb)
end
aggregate do |chunks|
# The return value for this block determines the value of the fact.
sum = 0
chunks.each_value do |i|
sum += i
end
sum
end
end