Feature #4700: Deploy Puppet environmentpath and environment config files - Installer - Foreman

Feature #4700

Deploy Puppet environmentpath and environment config files

Added by Dominic Cleal about 9 years ago. Updated over 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Dominic Cleal

Category:

Foreman modules

Target version:

1.6.0

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/puppet-puppet/pull/165

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Puppet 3.5 added support for an environmentpath (very much like our own default /etc/puppet/environments/) and 3.6 adds an environment.conf to configure the modulepath etc within each environment.

The installer should support deploying environments this style when possible, as it'll be the only option in Puppet 4.

https://groups.google.com/d/msg/puppet-dev/2QDi2ThnRJQ/EWrFJXa92i8J
https://tickets.puppetlabs.com/browse/PUP-1596

Related issues

Associated revisions

Revision 23978618 (diff)
Added by Dominic Cleal over 8 years ago

fixes #4700 - deploy directory environments on Puppet 3.6 or higher

- $server_dynamic_environments is deprecated when server_directory_environments
is enabled, set $server_environments = [] instead for a similar effect
- environment.conf deployed if custom manifest, config_version etc supplied to
puppet::server::env instead of puppet.conf fragment
- basemodulepath set in puppet.conf to the value of server_common_modules_path,
which had /etc/puppet/modules added to match the new Puppet default
- $environment_timeout added to puppet::server::env

History

#1 Updated by Dominic Cleal almost 9 years ago

Status changed from New to Ready For Testing

First part is up here: https://github.com/theforeman/puppet-puppet/pull/158

There are some further changes I noticed in the PR comments that need implementing, and finally we need to change the default to 'true' on Puppet 3.6+.