On Thu, 2014-03-06 at 20:16 -0800, Jeff McCune wrote:
This is just a continuation of a previous thread as to not hijack the
original discussion.
The question that needs a decision is, should post_resource_eval be
renamed given the context that it's currently implemented as a hook
into the
Eric,
I attempted to do some of that for the 2.7 series
https://www.onyxpoint.com/type-and-provider-execution-walkthrough/.
It might be a place/way to start.
Thanks,
Trevor
On Fri, Mar 7, 2014 at 10:31 AM, badgerious badge...@hotmail.com wrote:
There was a fair amount of bumbling to get
Trevor,
Cool! Something like an augmented version of the flowchart you've done up
would be handy.
Eric
On Friday, March 7, 2014 9:36:39 AM UTC-6, Trevor Vaughan wrote:
Eric,
I attempted to do some of that for the 2.7 series
On Thu, Mar 6, 2014 at 10:16 PM, Jeff McCune j...@puppetlabs.com wrote:
This is just a continuation of a previous thread as to not hijack the
original discussion.
The question that needs a decision is, should post_resource_eval be
renamed given the context that it's currently implemented as
You'd have to run through the entire catalog of resources in that case. It
would certainly work, but I'm not sure if it would actually do what you
want.
Trevor
On Fri, Mar 7, 2014 at 10:37 AM, badgerious badge...@hotmail.com wrote:
I should clarify my suggestion to say 'single @ class
I want to start a conversation about the package resource type and a bug
that goes back about 6 years. The current ticket
is https://tickets.puppetlabs.com/browse/PUP-1073 and relates to really old
tickets such as https://projects.puppetlabs.com/issues/973.
If I have gem 'x' and RPM 'x', I
On Fri, Mar 7, 2014 at 1:16 PM, Jeff McCune j...@puppetlabs.com wrote:
On Fri, Mar 7, 2014 at 7:45 AM, Nan Liu nan@gmail.com wrote:
On Thu, Mar 6, 2014 at 10:16 PM, Jeff McCune j...@puppetlabs.com wrote:
This is just a continuation of a previous thread as to not hijack the
original
I think this hits the nail on the head.
post_resources_eval == after all the resources of this type
post_resource_eval == after this resource
And, yes, we need both as well as post_catalog_eval!
I'd personnal prefer that there is not an explicit failure state between
these but, instead, state
If you could, please go +1 it in Jira for visibility.
I too would love to see this fixed.
Trevor
On Fri, Mar 7, 2014 at 1:55 PM, Drew Blessing drew.bless...@buckle.comwrote:
I want to start a conversation about the package resource type and a bug
that goes back about 6 years. The current
Long story short, allowing multiple resources to exist with the same title
but different providers is problematic. I've commented on this at
https://projects.puppetlabs.com/issues/1398#note-13 which explains why this
isn't trivial to solve. This is a limitation that is pretty core to how
Puppet
10 matches
Mail list logo
