On Tue, Aug 27, 2013 at 10:53 AM, Andy Parker <a...@puppetlabs.com> wrote:

> On Tue, Aug 27, 2013 at 10:21 AM, Jeff McCune <j...@puppetlabs.com> wrote:
>
>> If by "load everything" we're talking about something equivalent to
>> include <modulepath>/**/*.pp then that's silly and should be avoided.  It
>> would be a big step in the wrong direction, taking away control from the
>> end user rather than giving them more control over the system.
>>
>>
> It isn't "include <everything>" it is "import <everything>". Include would
> be a big step in the wrong direction because it would automatically put
> things in the catalog. Import, however, simply loads in things and makes
> them available. There may be other effects on manifests, however.
>

Right, I meant more the #include style of nearly everything else except
Puppet.  C, Apache conf, Bind conf, etc...

I should have said import.


> Markus suggested explicit loading.  Explicit loading is a much better
>> approach.  It's more efficient, it's well understood by everyone, and it
>> gives the end user explicit control over the behavior of the system.  It
>> comes at the cost of a bigger impact to all of our users, but that's OK.
>>  Puppet 4 shouldn't be that far off and we likely can make this behavior
>> gated on a feature flag for Puppet 3.
>>
>>
> Puppet 4 is most likely our next release after puppet 3.3. I still need to
> get another conversation going about what is in and out of scope for puppet
> 4. We have some ideas internal to puppet labs, but we need to get those
> communicated out and make the entire thing much clearer to ourselves.
> However, I'd like to keep this conversation a bit more focussed on the
> feasibility and technical aspects of this specific change.
>

Right.  Is it feasible to gate this on a feature flag, or do we not yet
know?

If we can't gate the behavior on a flag, then why shouldn't we wait until
we can make breaking changes?  What's the rush?

-Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-dev.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to