On Thursday, October 11, 2012 6:27:07 PM UTC-5, Jeff McCune wrote:
Yeah, but sometimes the need to manage both sides of the wrapper class is
un-avoidable. I often find this to be the case when I'm dealing with
interpreter packages like java, ruby, perl, python, etc... The classes
that
On Oct 11, 2012, at 7:09 AM, llowder llowde...@gmail.com wrote:
On Thursday, October 11, 2012 8:37:39 AM UTC-5, alcy wrote:
Hello,
I have a class like:
class wrapper {
include foo
include bar
include baz
}
And a node like:
node x {
include someclass
include wrapper
Hello,
On Thu, Oct 11, 2012 at 8:39 PM, Jeff McCune j...@puppetlabs.com wrote:
Yes, this is a perfect example of when to employ the anchor pattern. It's
also a perfect example of the bug we need to fix in puppet.
Class foo, bar, an baz will float off in the relationship graph because
class
On Thu, Oct 11, 2012 at 8:32 AM, Mohit Chawla mohit.chawla.bin...@gmail.com
wrote:
Hello,
On Thu, Oct 11, 2012 at 8:39 PM, Jeff McCune j...@puppetlabs.com wrote:
Yes, this is a perfect example of when to employ the anchor pattern. It's
also a perfect example of the bug we need to fix in
Thank you, that worked nicely !
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more
On Thursday, October 11, 2012 10:32:29 AM UTC-5, alcy wrote:
And although this might be a difficult question to give a generalized
(or rather, a slightly less technical) answer, but this behaviour of
floating off of the graph, is it easy to attribute this to particular
scenarios ?
Yes.
Hello John,
On Thu, Oct 11, 2012 at 11:53 PM, jcbollinger john.bollin...@stjude.org wrote:
Yes. When one class declares another, whether via the 'include' or
'require' function or via a parametrized-style declaration, that
(intentionally) does not establish any ordering relationship between
- Original Message -
From: Mohit Chawla mohit.chawla.bin...@gmail.com
To: puppet-users@googlegroups.com
Sent: Thursday, October 11, 2012 10:04:41 PM
Subject: Re: [Puppet Users] Re: Wrapper classes, ordering anchors
Hello John,
On Thu, Oct 11, 2012 at 11:53 PM, jcbollinger
Hello,
On Fri, Oct 12, 2012 at 2:44 AM, R.I.Pienaar r...@devco.net wrote:
i find the anchor pattern both a royal pain and too strict, i dont generally
care to bind classes between two resources but instead just before some
resource or class
class wrapper {
include one, two, three
- Original Message -
From: Mohit Chawla mohit.chawla.bin...@gmail.com
To: puppet-users@googlegroups.com
Sent: Thursday, October 11, 2012 10:31:28 PM
Subject: Re: [Puppet Users] Re: Wrapper classes, ordering anchors
Hello,
On Fri, Oct 12, 2012 at 2:44 AM, R.I.Pienaar r
, 2012 at 3:10 AM, R.I.Pienaar r...@devco.net wrote:
- Original Message -
From: Mohit Chawla mohit.chawla.bin...@gmail.com
To: puppet-users@googlegroups.com
Sent: Thursday, October 11, 2012 10:31:28 PM
Subject: Re: [Puppet Users] Re: Wrapper classes, ordering anchors
Hello,
On Fri
- Original Message -
From: Mohit Chawla mohit.chawla.bin...@gmail.com
To: puppet-users@googlegroups.com
Sent: Thursday, October 11, 2012 10:49:50 PM
Subject: Re: [Puppet Users] Re: Wrapper classes, ordering anchors
Weird, the only difference is I didn't define any relationship
To: puppet-users@googlegroups.com
Sent: Thursday, October 11, 2012 10:49:50 PM
Subject: Re: [Puppet Users] Re: Wrapper classes, ordering anchors
Weird, the only difference is I didn't define any relationship
between one, two, three, but made them all depend on wrapper individually
- Original Message -
From: Mohit Chawla mohit.chawla.bin...@gmail.com
To: puppet-users@googlegroups.com
Sent: Thursday, October 11, 2012 10:59:33 PM
Subject: Re: [Puppet Users] Re: Wrapper classes, ordering anchors
Hmm, thanks, I'll try upgrading the master to the same minor
Chawla mohit.chawla.bin...@gmail.com
To: puppet-users@googlegroups.com
Sent: Thursday, October 11, 2012 10:59:33 PM
Subject: Re: [Puppet Users] Re: Wrapper classes, ordering anchors
Hmm, thanks, I'll try upgrading the master to the same minor version
and see if it works differently, would
- Original Message -
From: Mohit Chawla mohit.chawla.bin...@gmail.com
To: puppet-users@googlegroups.com
Sent: Thursday, October 11, 2012 11:19:48 PM
Subject: Re: [Puppet Users] Re: Wrapper classes, ordering anchors
Hi, it works with code like in your paste. But check this out
Sent: Thursday, October 11, 2012 11:19:48 PM
Subject: Re: [Puppet Users] Re: Wrapper classes, ordering anchors
Hi, it works with code like in your paste. But check this out :
http://pastie.org/5037832, the original situation I found myself in,
and you can see the floating off behaviour again
On Fri, Oct 12, 2012 at 03:49:48AM +0530, Mohit Chawla wrote:
Hi, it works with code like in your paste. But check this out :
http://pastie.org/5037832, the original situation I found myself in,
and you can see the floating off behaviour again.
Because you are saying that Class[abc] should
Ah ! Having come across this before in my resource dependencies with
normal types (just correlating with some of the modules), this makes
it even clearer, thanks.
On Fri, Oct 12, 2012 at 4:19 AM, Stefan Schulte
stefan.schu...@taunusstein.net wrote:
On Fri, Oct 12, 2012 at 03:49:48AM +0530, Mohit
On Thu, Oct 11, 2012 at 3:26 PM, R.I.Pienaar r...@devco.net wrote:
- Original Message -
From: Mohit Chawla mohit.chawla.bin...@gmail.com
To: puppet-users@googlegroups.com
Sent: Thursday, October 11, 2012 11:19:48 PM
Subject: Re: [Puppet Users] Re: Wrapper classes, ordering
Also, for sake of concision, I should point out that chaining arrows can
accept both resource declarations and multi-resource references
(https://docs.puppetlabs.com/puppet/3/reference/lang_relationships.html#operands),
which gives you the option of a one-liner workaround:
class wrapper {
21 matches
Mail list logo
