linux/meta-cloud-services.git/recipes-support/facter, branch master

facter: relax Ruby version constraint for Ruby 4.x

2026-04-08T16:13:11+00:00

OE-core now ships Ruby 4.0.1 which exceeds the gemspec upper bound of < 4.0. Bump to < 5.0. Signed-off-by: Bruce Ashfield

facter: update to 4.10.0

2026-04-08T16:13:11+00:00

Signed-off-by: Bruce Ashfield

facter: update to 4.9.0

2024-10-09T23:30:19+00:00

This has been build tested only. This updates facter to a much newer release. It also adapts to copying versus patching in the gemspec (Which was pull from the facter repository): https://github.com/puppetlabs/facter/blob/main/facter.gemspec Signed-off-by: Bruce Ashfield

Puppet upstream upgrade to 5.4.0

2018-02-20T22:05:27+00:00

* Upstream to 5.4.0 [1][2][3][4][5] * Puppet 5 recipe is the official Puppet agent version with support for Ruby 2.4 [6] * Updated reference versions in the README file * Hiera isn’t separate from Puppet anymore [7]. * Do not install extlookup2hiera, it has been removed upstream * Hiera began as an independent Ruby library that worked with Puppet. Over time, it became a requirement and was even included in the puppet-agent package, but it was limited by its original design. * Removed puppet_3.7.3.bb recipe * Drop the superseded patches * Added init script * Added systemd script Facter 2.5 upstream release * Puppet 5 relays on Facter 3.10. Facter 3.10 reworks Facter 2.X code [8] in native code instead of Ruby gem. Facter 2.5 is still compatible with 5 series to help with Puppet 5 testing. * facter before 2.4.0 uses a deprecated Puppet settings API making `facter --puppet` no longer work with Puppet 4 or higher [9]. * Community, partner, and some of Puppet's internal testing workflows continue to use (ruby) Facter 2.4 [10], instead of native Facter 3, which is not (yet) available as a gem. * To help with Puppet 5 testing, we need to do a maintenance release in the Facter 2 series. [1] https://docs.puppet.com/puppet/5.0/release_notes.html [2] https://docs.puppet.com/puppet/5.1/release_notes.html [3] https://docs.puppet.com/puppet/5.2/release_notes.html [4] https://docs.puppet.com/puppet/5.3/release_notes.html [5] https://docs.puppet.com/puppet/5.4/release_notes.html [6] https://puppet.com/docs/puppet/4.10/hiera_intro.html [7] https://tickets.puppetlabs.com/browse/PA-1107 [8] https://github.com/puppetlabs/facter/tree/3.10.x [9] http://metadata.ftp-master.debian.org/changelogs/main/p/puppet/puppet_5.1.0-1_changelog [10] https://tickets.puppetlabs.com/browse/FACT-1630 Signed-off-by: Pablo Saavedra Signed-off-by: Bruce Ashfield

puppet: move to base layer

2015-08-20T17:38:48+00:00

Puppet can be used by many 'cloud services', it is not openstack specific, so moving puppet and puppet related recipes to the meta-cloud-services base layer. This allows either internal sub-layers found in meta-cloud-services or external layers to include meta-cloud-services without being burdened by bbappends and configs found in meta-openstack. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield