Project

General

Profile

Actions

Feature #2993

closed

Improve interoperability with external modules

Added by Greg Sutcliffe over 10 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

This discussion was started on https://github.com/theforeman/foreman-installer/pull/46 but stalled, so we agreed to discuss possible implementations here. The goal is to more easily be able to drop in modules like 'puppetdb' which are not really within our remit as a Foreman installer, but which might well want to be used by end users. A few relevant bits:

Ewoud:

I agree with @Dominic Cleal that further integration should be done. You should also set $puppet::server::storeconfigs and $puppet::server::storeconfigs_backend. Then I think you could even ignore the puppetdb:master::config since puppet::server will ensure the correct settings as well.

Dominic:

@Ewoud Kohl van Wijngaarden you'll still need puppetdb::master::config to deploy routes.yaml IIRC, but I turn off its management of puppet.conf (via inifile) and set the storeconfig params on the puppet module as you say.

Ewoud:

Last week I tried setting it up on one host and noticed that I have to include the puppetdb setup before foreman since puppetdb uses class{'postgresql::server'] where foreman uses include postgresql::server. Thought this was the best place to document it for now.

Actions #1

Updated by Anonymous almost 7 years ago

  • Status changed from New to Resolved

this is better now.

Actions

Also available in: Atom PDF