On Monday, May 19, 2014 6:48:36 AM UTC-5, David Portabella wrote:
>
>
>
>
>> so, one specific example,
>>> someone (not me) implemented a class tomcat with parameters port and
>>> ssl_port.
>>> I want to use that class,
>>> and I want that the ssl_port is always port + 1 (I don't want this
On 2014-14-04 16:43, jcbollinger wrote:
On Friday, April 11, 2014 10:10:37 PM UTC-5, David Portabella wrote:
I didn't know about this /evaluation-order dependency./
Why does this "evaluation-order dependency" exists in puppet?
Do you mean this particular one, or evaluation-order dep
> so, one specific example,
>> someone (not me) implemented a class tomcat with parameters port and
>> ssl_port.
>> I want to use that class,
>> and I want that the ssl_port is always port + 1 (I don't want this to be
>> configurable in hiera)
>>
> so, in my hiera data, I will specify port
On Tuesday, April 15, 2014 9:21:38 AM UTC-5, David Portabella wrote:
>
> Ok, I see.
>
> Thanks for all this discussion!
>
>
> > No, you *never* need to use parameterized classes.
> > If you are determined to avoid resource-like class declarations,
> > then you can replace each parameterized cl
On 04/15/2014 04:21 PM, David Portabella wrote:
> for a java/scala software developer like me, this does not look a good,
> because it makes it more difficult to unit test.
> maybe with puppet it is easy to build and pass different hiera data for
> unit testing?
Sure, that shouldn't be (much) wors
Ok, I see.
Thanks for all this discussion!
> No, you *never* need to use parameterized classes.
> If you are determined to avoid resource-like class declarations,
> then you can replace each parameterized class in your manifest set with a
non-parameterized version that obtains its data via d
On Friday, April 11, 2014 10:10:37 PM UTC-5, David Portabella wrote:
>
> I didn't know about this *evaluation-order dependency.*
> Why does this "evaluation-order dependency" exists in puppet?
>
Do you mean this particular one, or evaluation-order dependencies in
general?
Anyway, I started to
I didn't know about this *evaluation-order dependency.*
Why does this "evaluation-order dependency" exists in puppet?
Is it done in purpose, or it is a technical problem of the puppet
implementation?
Do you have an example where we would want to use this evaluation-order
dependency?
Or could pupp
On Thursday, April 3, 2014 10:31:40 AM UTC-5, David Portabella wrote:
>
> *> **Agree with John that you want to completely avoid using the
> parameterized style declaration of classes. Better to use
> 'include' statements and set all of your params in Hiera. *
>
> That's an interesting discuss
*> **Agree with John that you want to completely avoid using the
parameterized style declaration of classes. Better to use
'include' statements and set all of your params in Hiera. *
That's an interesting discussion,
but that's not the point of this post.
the point of this post, as I understa
On 4/2/14, 3:23 PM, jcbollinger wrote:
>
>
> On Wednesday, April 2, 2014 4:57:39 AM UTC-5, David Portabella wrote:
>
> Oh My God!
>
> you mean that "it's not a bug, it is a feature" ?
>
>
>
> It is not a feature in the sense of a desired outcome, but it /is/ the
> intended behavior.
On Wednesday, April 2, 2014 4:57:39 AM UTC-5, David Portabella wrote:
>
> Oh My God!
>
> you mean that "it's not a bug, it is a feature" ?
>
>
It is not a feature in the sense of a desired outcome, but it *is* the
intended behavior. Specifically, if there is any parameterized-style
declaratio
Oh My God!
you mean that "it's not a bug, it is a feature" ?
On Wednesday, April 2, 2014 11:36:34 AM UTC+2, Jose Luis Ledesma wrote:
>
> hi,
>
>
> from:
>
>
> http://docs.puppetlabs.com/puppet/latest/reference/lang_classes.html#declaring-classes
>
> Include-Like vs. Resource-Like
>
> Puppet has
Thanks Jose for your answer.
The note from the doc is quite vague in my opinion. I would understand that
class c1 {
class { 'c2' : }
require "c3"
}
effectively mixes the two behaviors, but
class { 'c1' : }
class c1 {
require "c2"
}
should not be a case of mixed behavior. The followin
hi,
from:
http://docs.puppetlabs.com/puppet/latest/reference/lang_classes.html#declaring-classes
Include-Like vs. Resource-Like
Puppet has two main ways to declare classes: include-like and resource-like.
*Note:* These two behaviors *should not be mixed* for a given class.
Puppet's behavior w
Hi,
I've got the following code that works as expected:
class { "c1": }
class { "c2": }
class c1 {
notice "+++"
}
class c2 {
require "c1"
notice "+++"
}
But switching the declaration order of class c1 and c2:
class { "c2": }
class { "c1": }
class c1 {
notice "+++"
}
class c2 {
req
16 matches
Mail list logo
