Announce: Facter 2.0.1

[Eric Sorenson]

Released April 1, 2014. (RC1: February 28; RC2: March 12; RC3: March 25; RC4: March 28.)

Facter 2.0.1 is the first release in the Facter 2 series.

Headline Features
- Fact values can now be arbitrarily complex data structures instead of simple strings.
- There’s a new API for adding facts, which enables structured facts and allows fact values to be built up across multiple ‘chunks’ of code. (see http://docs.puppetlabs.com/facter/2.0/fact_overview.html for the full details )

Additional Changes
- There are some backwards-incompatible changes to fact resolutions which were queued up for a major semver bump.
- Code that was deprecated in the Facter 1.x series is now gone, both internal code as well as some facts (‘ldapname’, ‘memorytotal’, ‘selinux_mode’)
- Facter no longer supports Ruby 1.8.5.

See the full release notes here: http://docs.puppetlabs.com/facter/2.0/release_notes.html
Get Facter 2 by following the instructions here (but install the Facter package instead of Puppet): http://docs.puppetlabs.com/guides/installation.html


Eric Sorenson - eric.s...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles

[Chris Handy]

I am really looking forward to the complex data structures.  I was wondering how this will work with hiera going forward, specifically with the hiera.yaml hierarchy?  Lets say that my hierarchy uses "role" and "app" facts to determine which level of the hierarchy to invoke.  Would I be able to use an array of "apps" and have it match somehow?  I could also see how this would allow multiple "roles" to be defined as a fact and invoked as well.