date:20170926

Re: [Puppet Users] Is hiera broken in FOSS Puppet 3.7.2?

2017-09-26 Thread Ramin K

Puppet 4 ships as an all in one package so you can even run it on
Centos5 since it's ships with it's own Ruby, etc.

http://yum.puppetlabs.com/el/6/PC1/x86_64/

Ramin

On 9/26/17 12:32 PM, Peter Berghold wrote:

I was afraid that would be an answer I got... :-)

There are plans to move to Puppet 4 where I know all this works but
given I have to support all this on RHEL 6.x there may be some obstacles
there. I would LOVE to wave a magic wand and make Puppet 3.x go away

So.. 3.8 eh? There's something to investigate

On Tue, Sep 26, 2017 at 1:46 PM Rob Nelson > wrote:

If I had to guess, it would be that the merge settings either don't
exist or are buggy in 3.7.2. 3.8 was EOL in December last year, if
you have to stick with 3 I'd suggest at least trying it with 3.8.

On Tue, Sep 26, 2017 at 12:35 PM Peter Berghold
> wrote:

Seeing things like doing a hiera lookup inside a manifest such as

$somevar = hiera('randomvalue','notfound')

returning nils and other odd behavior.

I have a hiera.yaml file that looks like:

---
:backends:
- yaml
:merge_behavior: deeper
:deep_merge_options: {}
:yaml:
:datadir: "/etc/puppet/environments/%{environment}/hieradata"
:hierarchy:
- "function/${::facts.host_function}"
- "datacenter/%{::facts.sitename}"
- "nodes/%{fqdn}"
- "common_classes"
- "common"

and yet I see both the nodes and common_classes being ignored.

Of more concern to me is I'm trying to set values such as

somemod::parms::value1: somevalue

and that's being ignored.

Puppet.conf is configured correctly because it *is* finding a
class list in common.yaml but nowhere else.

Thoughts?

--
You received this message because you are subscribed to the

Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to puppet-users+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/puppet-users/CAArvnv2ssHekfEX9Asi4eEriQqJ0ohgbyg%3DGSvM%2B0L_eGU2RUw%40mail.gmail.com

.
For more options, visit https://groups.google.com/d/optout.

--
Rob Nelson

--
You received this message because you are subscribed to the Google

Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to puppet-users+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/puppet-users/CAC76iT8LVV3HzOC-9eKDyHJKhJTdGjEY9j5jWYqafW8BY6GYnQ%40mail.gmail.com

.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to puppet-users+unsubscr...@googlegroups.com
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAArvnv1Mnqs1B_ZAUUFSb1xSifUu6X%2Birj41C9j1UJa%2Bprg2QQ%40mail.gmail.com
.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/c08d2935-2f5f-f852-1e87-273485e22c56%40badapple.net.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is hiera broken in FOSS Puppet 3.7.2?

2017-09-26 Thread Rob Nelson

If it helps, I use Puppet 4 and RHEL6 all the time!


Rob Nelson
rnels...@gmail.com

On Tue, Sep 26, 2017 at 3:32 PM, Peter Berghold 
wrote:

> I was afraid that would be an answer I got... :-)
>
> There are plans to move to Puppet 4 where I know all this works but given
> I have to support all this on RHEL 6.x there may be some obstacles there.
> I would LOVE to wave a magic wand and make Puppet 3.x go away
>
> So.. 3.8 eh?  There's something to investigate
>
>
> On Tue, Sep 26, 2017 at 1:46 PM Rob Nelson  wrote:
>
>> If I had to guess, it would be that the merge settings either don't exist
>> or are buggy in 3.7.2. 3.8 was EOL in December last year, if you have to
>> stick with 3 I'd suggest at least trying it with 3.8.
>>
>> On Tue, Sep 26, 2017 at 12:35 PM Peter Berghold 
>> wrote:
>>
>>> Seeing things like doing a hiera lookup inside a manifest such as
>>>
>>> $somevar = hiera('randomvalue','notfound')
>>>
>>> returning nils and other odd behavior.
>>>
>>> I have a hiera.yaml file that looks like:
>>>
>>> ---
>>> :backends:
>>>   - yaml
>>> :merge_behavior: deeper
>>> :deep_merge_options: {}
>>> :yaml:
>>>   :datadir: "/etc/puppet/environments/%{environment}/hieradata"
>>> :hierarchy:
>>>   - "function/${::facts.host_function}"
>>>   - "datacenter/%{::facts.sitename}"
>>>   - "nodes/%{fqdn}"
>>>   - "common_classes"
>>>   - "common"
>>>
>>> and yet I see both the nodes and common_classes being ignored.
>>>
>>> Of more concern to me is I'm trying to set values such as
>>>
>>> somemod::parms::value1:  somevalue
>>>
>>> and that's being ignored.
>>>
>>> Puppet.conf is configured correctly because it *is* finding a class list
>>> in common.yaml but nowhere else.
>>>
>>>
>>> Thoughts?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Puppet Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to puppet-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/puppet-users/CAArvnv2ssHekfEX9Asi4eEriQqJ0o
>>> hgbyg%3DGSvM%2B0L_eGU2RUw%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> Rob Nelson
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/puppet-users/CAC76iT8LVV3HzOC-9eKDyHJKhJTdGjEY9j5jWYqafW8BY6
>> GYnQ%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/puppet-users/CAArvnv1Mnqs1B_ZAUUFSb1xSifUu6X%
> 2Birj41C9j1UJa%2Bprg2QQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAC76iT-PHcgSVZgFOkBXwQ9OyUavE6wJgAcBWw8%3D-4RjLJg0CQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is hiera broken in FOSS Puppet 3.7.2?

2017-09-26 Thread Peter Berghold

I was afraid that would be an answer I got... :-)

There are plans to move to Puppet 4 where I know all this works but given I
have to support all this on RHEL 6.x there may be some obstacles there.   I
would LOVE to wave a magic wand and make Puppet 3.x go away

So.. 3.8 eh?  There's something to investigate


On Tue, Sep 26, 2017 at 1:46 PM Rob Nelson  wrote:

> If I had to guess, it would be that the merge settings either don't exist
> or are buggy in 3.7.2. 3.8 was EOL in December last year, if you have to
> stick with 3 I'd suggest at least trying it with 3.8.
>
> On Tue, Sep 26, 2017 at 12:35 PM Peter Berghold 
> wrote:
>
>> Seeing things like doing a hiera lookup inside a manifest such as
>>
>> $somevar = hiera('randomvalue','notfound')
>>
>> returning nils and other odd behavior.
>>
>> I have a hiera.yaml file that looks like:
>>
>> ---
>> :backends:
>>   - yaml
>> :merge_behavior: deeper
>> :deep_merge_options: {}
>> :yaml:
>>   :datadir: "/etc/puppet/environments/%{environment}/hieradata"
>> :hierarchy:
>>   - "function/${::facts.host_function}"
>>   - "datacenter/%{::facts.sitename}"
>>   - "nodes/%{fqdn}"
>>   - "common_classes"
>>   - "common"
>>
>> and yet I see both the nodes and common_classes being ignored.
>>
>> Of more concern to me is I'm trying to set values such as
>>
>> somemod::parms::value1:  somevalue
>>
>> and that's being ignored.
>>
>> Puppet.conf is configured correctly because it *is* finding a class list
>> in common.yaml but nowhere else.
>>
>>
>> Thoughts?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/CAArvnv2ssHekfEX9Asi4eEriQqJ0ohgbyg%3DGSvM%2B0L_eGU2RUw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Rob Nelson
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAC76iT8LVV3HzOC-9eKDyHJKhJTdGjEY9j5jWYqafW8BY6GYnQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAArvnv1Mnqs1B_ZAUUFSb1xSifUu6X%2Birj41C9j1UJa%2Bprg2QQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is hiera broken in FOSS Puppet 3.7.2?

2017-09-26 Thread Rob Nelson

If I had to guess, it would be that the merge settings either don't exist
or are buggy in 3.7.2. 3.8 was EOL in December last year, if you have to
stick with 3 I'd suggest at least trying it with 3.8.

On Tue, Sep 26, 2017 at 12:35 PM Peter Berghold 
wrote:

> Seeing things like doing a hiera lookup inside a manifest such as
>
> $somevar = hiera('randomvalue','notfound')
>
> returning nils and other odd behavior.
>
> I have a hiera.yaml file that looks like:
>
> ---
> :backends:
>   - yaml
> :merge_behavior: deeper
> :deep_merge_options: {}
> :yaml:
>   :datadir: "/etc/puppet/environments/%{environment}/hieradata"
> :hierarchy:
>   - "function/${::facts.host_function}"
>   - "datacenter/%{::facts.sitename}"
>   - "nodes/%{fqdn}"
>   - "common_classes"
>   - "common"
>
> and yet I see both the nodes and common_classes being ignored.
>
> Of more concern to me is I'm trying to set values such as
>
> somemod::parms::value1:  somevalue
>
> and that's being ignored.
>
> Puppet.conf is configured correctly because it *is* finding a class list
> in common.yaml but nowhere else.
>
>
> Thoughts?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAArvnv2ssHekfEX9Asi4eEriQqJ0ohgbyg%3DGSvM%2B0L_eGU2RUw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Rob Nelson

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAC76iT8LVV3HzOC-9eKDyHJKhJTdGjEY9j5jWYqafW8BY6GYnQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Question regarding Puppet4 class params and Hiera5

2017-09-26 Thread Sean

Hi David, thanks for your reply.

I can see where I may have confused the intent of my questions with too 
much information.  If someone using the class were to declare something 
like:

class { 'complex':
  enable_feature1 => false,
  class_incl_list  => [ 'complex::redhat::subclass1', ],
}

Will subclass1 obtain the value of enable_feature1 from the above 
declaration?  Suppose the module default in data/common.yaml for 
enable_feature1 is true.

On Tuesday, September 26, 2017 at 12:13:42 PM UTC-4, David Schmitt wrote:
>
>
>
> On Tue, Sep 26, 2017 at 4:01 PM Sean  
> wrote:
>
>> Greetings,
>>
>> I have read searched and read several threads in the list regarding using 
>> hiera, automatic lookup, and class params.  Some of them, I'm thinking 
>> relate to Puppet3 and prior, and I admit I'm struggling a bit with weeding 
>> through the information that's appropriate to my scenario of versions.  
>> Please bear with me.  I am attempting to build a module that will use Hiera 
>> data layers and get away from the params.pp pattern.  The hope is that 
>> customers can use their environment hiera data if they choose, global data 
>> from an ENC, accept the default module layer data or use resource 
>> definition and supply data directly.  Unfortunately the module is complex 
>> and has many sublcasses, the init.pp looks something like:
>>
>> class complex (
>>   Array $class_incl_list,
>>   Array $class_excl_list,
>>   Boolean $enable_feature1,
>>   ...more params that subclasses might use...
>> ) {
>>
>>   validate_array($class_incl_list)
>>   validate_array($class_excl_list)
>>
>
> Since you have already specified `Array` on the params, you can skip the 
> `validate_array()` call here.
>  
>
>>
>>   $local_incl_list = array_subtract($class_incl_list, $class_excl_list)
>>
>>   include $local_incl_list
>>
>> }
>>
>> The class arrays are strings of fully qualified subclass names, e.g. [ 
>> 'complex::redhat::subclass1', 'complex::redhat::subclass2', ] etc. 
>>
>> Is there a benefit to actually using class params or declaring all 
>> references to class variables directly as fully qualified in the subclasses?
>>
>
> `include` is necessary to make the class - and its resources - available 
> in the catalog. It has no influence over variable namespacing/scope.
>
> If that doesn't answer your question, likely I haven't really understood 
> what you were asking.
>  
>
>> Here's a simplified example subclass, and yes the example is silly, if we 
>> enable/disable a feature in puppet code, why not just exclude the subclass 
>> altogether. 
>>
>
> If you need to have stuff done to *remove* a feature, this pattern is 
> absolutely fine!
>
>  
>
>> Typically, that is what happens, but I was failing to find any other 
>> simplistic examples to provide.
>>
>> class complex::redhat::subclass1 (
>>   Boolean $enable_feature1,
>> ) {
>>
>>   if $enable_feature1 {
>> notify("${::osfamily} Feature 1 is enabled")
>>   } else {
>> notify("${::osfamily} Feature 1 is disabled")
>>   }
>>
>> }
>>
>>
>> Would I be better off removing the class param and using 
>> $::complex::enable_feature1 in the conditional?
>>
>
> Yes.
>  
>
>>   The subclasses aren't really meant to be called by the end-user 
>> directly, so I would never expect to see someone doing a resource 
>> declaration of a subclass, but I would expect to see a user doing a 
>> resource declaration of the main class and supplying the enable_feature1 
>> boolean with it.
>>
>> Thanks for your thoughts and input.
>>
>
>
> Cheers, David 
>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to puppet-users...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/f374a512-e5a1-4933-bc0e-405bbc8b44f9%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/94f61b8e-94b1-4023-bb84-7eb64de07fa5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Is hiera broken in FOSS Puppet 3.7.2?

2017-09-26 Thread Peter Berghold

Seeing things like doing a hiera lookup inside a manifest such as

$somevar = hiera('randomvalue','notfound')

returning nils and other odd behavior.

I have a hiera.yaml file that looks like:

---
:backends:
  - yaml
:merge_behavior: deeper
:deep_merge_options: {}
:yaml:
  :datadir: "/etc/puppet/environments/%{environment}/hieradata"
:hierarchy:
  - "function/${::facts.host_function}"
  - "datacenter/%{::facts.sitename}"
  - "nodes/%{fqdn}"
  - "common_classes"
  - "common"

and yet I see both the nodes and common_classes being ignored.

Of more concern to me is I'm trying to set values such as

somemod::parms::value1:  somevalue

and that's being ignored.

Puppet.conf is configured correctly because it *is* finding a class list in
common.yaml but nowhere else.


Thoughts?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAArvnv2ssHekfEX9Asi4eEriQqJ0ohgbyg%3DGSvM%2B0L_eGU2RUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Question regarding Puppet4 class params and Hiera5

2017-09-26 Thread David Schmitt

On Tue, Sep 26, 2017 at 4:01 PM Sean  wrote:

> Greetings,
>
> I have read searched and read several threads in the list regarding using
> hiera, automatic lookup, and class params.  Some of them, I'm thinking
> relate to Puppet3 and prior, and I admit I'm struggling a bit with weeding
> through the information that's appropriate to my scenario of versions.
> Please bear with me.  I am attempting to build a module that will use Hiera
> data layers and get away from the params.pp pattern.  The hope is that
> customers can use their environment hiera data if they choose, global data
> from an ENC, accept the default module layer data or use resource
> definition and supply data directly.  Unfortunately the module is complex
> and has many sublcasses, the init.pp looks something like:
>
> class complex (
>   Array $class_incl_list,
>   Array $class_excl_list,
>   Boolean $enable_feature1,
>   ...more params that subclasses might use...
> ) {
>
>   validate_array($class_incl_list)
>   validate_array($class_excl_list)
>

Since you have already specified `Array` on the params, you can skip the
`validate_array()` call here.


>
>   $local_incl_list = array_subtract($class_incl_list, $class_excl_list)
>
>   include $local_incl_list
>
> }
>
> The class arrays are strings of fully qualified subclass names, e.g. [
> 'complex::redhat::subclass1', 'complex::redhat::subclass2', ] etc.
>
> Is there a benefit to actually using class params or declaring all
> references to class variables directly as fully qualified in the subclasses?
>

`include` is necessary to make the class - and its resources - available in
the catalog. It has no influence over variable namespacing/scope.

If that doesn't answer your question, likely I haven't really understood
what you were asking.


> Here's a simplified example subclass, and yes the example is silly, if we
> enable/disable a feature in puppet code, why not just exclude the subclass
> altogether.
>

If you need to have stuff done to *remove* a feature, this pattern is
absolutely fine!



> Typically, that is what happens, but I was failing to find any other
> simplistic examples to provide.
>
> class complex::redhat::subclass1 (
>   Boolean $enable_feature1,
> ) {
>
>   if $enable_feature1 {
> notify("${::osfamily} Feature 1 is enabled")
>   } else {
> notify("${::osfamily} Feature 1 is disabled")
>   }
>
> }
>
>
> Would I be better off removing the class param and using
> $::complex::enable_feature1 in the conditional?
>

Yes.


>   The subclasses aren't really meant to be called by the end-user
> directly, so I would never expect to see someone doing a resource
> declaration of a subclass, but I would expect to see a user doing a
> resource declaration of the main class and supplying the enable_feature1
> boolean with it.
>
> Thanks for your thoughts and input.
>


Cheers, David

> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/f374a512-e5a1-4933-bc0e-405bbc8b44f9%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CALF7fHadtWaMaxmHc%2BSf8bfk10ShQ8aNAv3d3oC_Nc-D8GxBxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Question regarding Puppet4 class params and Hiera5

2017-09-26 Thread Sean

Greetings,

I have read searched and read several threads in the list regarding using 
hiera, automatic lookup, and class params.  Some of them, I'm thinking 
relate to Puppet3 and prior, and I admit I'm struggling a bit with weeding 
through the information that's appropriate to my scenario of versions.  
Please bear with me.  I am attempting to build a module that will use Hiera 
data layers and get away from the params.pp pattern.  The hope is that 
customers can use their environment hiera data if they choose, global data 
from an ENC, accept the default module layer data or use resource 
definition and supply data directly.  Unfortunately the module is complex 
and has many sublcasses, the init.pp looks something like:

class complex (
  Array $class_incl_list,
  Array $class_excl_list,
  Boolean $enable_feature1,
  ...more params that subclasses might use...
) {

  validate_array($class_incl_list)
  validate_array($class_excl_list)

  $local_incl_list = array_subtract($class_incl_list, $class_excl_list)

  include $local_incl_list

}

The class arrays are strings of fully qualified subclass names, e.g. [ 
'complex::redhat::subclass1', 'complex::redhat::subclass2', ] etc. 

Is there a benefit to actually using class params or declaring all 
references to class variables directly as fully qualified in the subclasses?

Here's a simplified example subclass, and yes the example is silly, if we 
enable/disable a feature in puppet code, why not just exclude the subclass 
altogether.  Typically, that is what happens, but I was failing to find any 
other simplistic examples to provide.

class complex::redhat::subclass1 (
  Boolean $enable_feature1,
) {

  if $enable_feature1 {
notify("${::osfamily} Feature 1 is enabled")
  } else {
notify("${::osfamily} Feature 1 is disabled")
  }

}


Would I be better off removing the class param and using 
$::complex::enable_feature1 in the conditional?  The subclasses aren't 
really meant to be called by the end-user directly, so I would never expect 
to see someone doing a resource declaration of a subclass, but I would 
expect to see a user doing a resource declaration of the main class and 
supplying the enable_feature1 boolean with it.

Thanks for your thoughts and input.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/f374a512-e5a1-4933-bc0e-405bbc8b44f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: puppet disadvantages

2017-09-26 Thread Anirban Paul


https://jjasghar.github.io/blog/2013/06/26/ansible-vs-chef-vs-puppet/

On Monday, September 21, 2015 at 6:47:37 PM UTC+5:30, Sindhujit Ganguly 
wrote:
>
> Hi,
> Can someone tell me the disadvantages of Puppet GUI? Why is Puppet 
> slow to changes and customer requests as compared to Ansible and Salt?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1dd93f0f-ce77-4855-94f8-db5f8c7fa9c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet 5 server for Debian Stretch

2017-09-26 Thread Jonas Esbjørn Engell

Hi,

I know that the puppet 5 agent have been released for Debian Stretch, but I 
can't seem to find the puppetserver packages in the repository. Do anyone 
know of any plans/ETAs for support of the puppetserver on Debian Stretch?

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/c17bf015-7da0-4049-9b13-067b51fa239c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Is hiera broken in FOSS Puppet 3.7.2?

Re: [Puppet Users] Is hiera broken in FOSS Puppet 3.7.2?

Re: [Puppet Users] Is hiera broken in FOSS Puppet 3.7.2?

Re: [Puppet Users] Is hiera broken in FOSS Puppet 3.7.2?

Re: [Puppet Users] Question regarding Puppet4 class params and Hiera5

[Puppet Users] Is hiera broken in FOSS Puppet 3.7.2?

Re: [Puppet Users] Question regarding Puppet4 class params and Hiera5

[Puppet Users] Question regarding Puppet4 class params and Hiera5

[Puppet Users] Re: puppet disadvantages

[Puppet Users] Puppet 5 server for Debian Stretch

10 matches

Site Navigation

Mail list logo

Footer information