Project

General

Profile

Actions

Feature #2414

closed

Remove Puppet from Foreman core

Added by Dominic Cleal over 11 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Normal
Category:
Puppet integration
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

We need to complete removing the Puppet dependency from Foreman core, so all Puppet usage is in the smart proxy only. This will make it optional for people who don't use Puppet, plus avoid conflicts we've seen when loading Puppet as a library into the full Rails application (monkey patching).

Some tasks:

1. Reports need to be parsed in the report handler, then uploaded as JSON etc. (app/models/report.rb)
2. Fact uploads need to be hashes only, no Puppet::Node::Facts (app/models/host/managed.rb)
3. PuppetSetting checks the PUPPETVERSION constant (lib/puppet_setting.rb)


Related issues 6 (1 open5 closed)

Related to Foreman - Bug #2413: NoMethodError on Puppet 3.2 and Ruby 1.9.2Closed04/19/2013Actions
Related to Foreman - Support #2435: Unable to authentication with LDAP server using ldapsClosedActions
Related to Foreman - Bug #2448: "vm is required for this operation" when viewing oVirt VMs with Puppet 3.2ResolvedDominic Cleal05/01/2013Actions
Related to Foreman - Bug #2461: Cannot create a host without a puppet proxyClosedGreg Sutcliffe05/06/2013Actions
Related to Foreman - Bug #3030: Facter isn't loaded, but is referenced in DB migrations etc.ClosedGreg Sutcliffe09/05/2013Actions
Related to Foreman - Bug #3236: prod2dev assumes all production tables exist in developmentNew10/10/2013Actions
Actions

Also available in: Atom PDF