Project

General

Profile

Feature #11992

Support loading Puppet from AIO packages

Added by Dominic Cleal almost 6 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Puppet
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

The smart proxy supports Puppet 4 loaded in the same Ruby environment (#11599), e.g. installed via a gem or some OS packages, but does not support Puppet installed with AIO packaging. In this instance, it would be unable to require 'puppet' as it would be installed in a non-standard path.


Related issues

Related to Smart Proxy - Bug #11599: Parsing environments/manifests in Puppet 4 failsClosed2015-08-28
Related to Smart Proxy - Feature #13667: puppet_proxy and puppetca modules load puppet gem in puppet 4.0 and higher environments Closed2016-02-11
Blocks Foreman - Tracker #8447: Puppet 4 supportClosed2014-11-19

History

#1 Updated by Dominic Cleal almost 6 years ago

#2 Updated by Dominic Cleal almost 6 years ago

  • Related to Bug #11599: Parsing environments/manifests in Puppet 4 fails added

#3 Updated by Dominic Cleal almost 6 years ago

Vaguely related.. https://groups.google.com/forum/#!msg/foreman-dev/4PoI3PyndYg/FL3gz6rYJgAJ touches on how implementing support for AIO and Puppet 4 could permit dropping of Ruby 1.8.7 support eventually in the smart proxy.

Suggestions in the thread are to implement Puppet 4 and AIO support in kafo_parsers and have the smart proxy use that library.

#4 Updated by Dmitri Dolguikh over 5 years ago

  • Related to Feature #13667: puppet_proxy and puppetca modules load puppet gem in puppet 4.0 and higher environments added

#5 Updated by Dominic Cleal over 5 years ago

  • Status changed from New to Rejected

Support for loading Puppet from AIO packages will not be added, but instead ticket #13667 tracks using the Puppet Server API to retrieve all necessary information.

Also available in: Atom PDF