Issue #7749 has been updated by Jeff McCune.

For the watchers of this ticket, as part of the work in 7749, the behavior of 
Telly is that ~/.puppet.conf is merged with /etc/puppet/puppet.conf.  We've 
decided this is undesirable and complicates the problem of loading extension 
code so we're going to undo this specific behavior change in Telly.

Please see #15337 for more information.  Please add comments related to the 
configuration file merging in #15337 rather than this ticket.
----------------------------------------
Refactor #7749: Bootstrapping Puppet in Ruby code has nasty scope cycles...
https://projects.puppetlabs.com/issues/7749#change-66181

Author: Daniel Pittman
Status: Merged - Pending Release
Priority: High
Assignee: Chris Price
Category: 
Target version: 3.0.0
Affected Puppet version: 
Keywords: 
Branch: https://github.com/puppetlabs/puppet/pull/571


So, in debugging an issue using code during early startup of Puppet, I found 
out that we have some very strange run-scope dependencies in bootstrapping.

Specifically, we depend on *runtime* code in `Puppet::Util::CommandLine` and 
`Puppet::Application` executing before we can safely execute *load* time code 
in `Puppet`.

This manifests as strange defaults in the configuration, because the run mode 
is configured in P::A during that run-scope code, but the defaults load in 
puppet earlier than that.

This also makes it difficult to just `require 'puppet'` and have things 
actually work.  Coupled with a desire to be able to change run mode on the fly, 
and a longer term need for things that Faces abstract over to act as if in a 
run mode without the current hard-coded dependency, we kind of need to get this 
resolved.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to