Re: [Puppet Users] What do you use the 'group' attribute for when using the acl module?

Hi Paul, On Tue, Sep 9, 2014 at 11:30 AM, Paul Chernoch wrote: > The *acl *module has a parameter named '*group*' which takes a list of > users, groups or SIDs. > What is it for? When would I need it? > Windows Security Descriptors support a group to allow for POSIX emulation. Here's some date

Re: [Puppet Users] Duplicate Declarations - Puppet

On 09/08/2014 05:27 PM, Warren Clarke wrote: > Hi Pedro, > > A work around would be to declare the resource as follows in your > module(s): > > if !defined (File['path_to_your_directory']) { > file { 'path_to_your_directory' : > ensure = directory, > } > } > > That should resolve the "Dupli

Re: [Puppet Users] Type inheritance

Hi, well, no, there is currently no way to implement effective subtypes or create an inheritance hierarchy at this point. Not that it's not wanted - we could have made good use of such a for years. Some things are really hard to solve with the current RAL model. Fortunately, purging is usually no

[Puppet Users] Using exported resources as data containers?

I have a difficult-to-manage application which does not implement a conf.d or include syntax in its configuration, but requires a bunch of config snippets that contain information only on groups of other servers. I've been dealing with this by generating the config snippets from templates on

Re: [Puppet Users] Best method to query role specific data when using roles/profiles + hiera as an ENC

Hiera is called each time you query it, or because of the auto lookup, so if you set up a role variable in site.pp you can use it in next queries. I use this method ;) El 09/09/2014 23:03, "JeremyCampbell" escribió: > I would expect that the role has to be set before hiera is queried or am I >

Re: [Puppet Users] Best method to query role specific data when using roles/profiles + hiera as an ENC

You have 2 hierarchies, one flat that is the classifier that contains fqdn.yaml; each "fqdn.yaml" defined what is the role of the current fqdn. This hierarchy is filled when you deploy a server (via a webservice, manually or what you want) The 2nd hierarchy is what you have today. Le 09/09/201

Re: [Puppet Users] Best method to query role specific data when using roles/profiles + hiera as an ENC

I would expect that the role has to be set before hiera is queried or am I missing something? I don't understand how that would work. On Tuesday, September 9, 2014 8:11:08 PM UTC+2, Jose Luis Ledesma wrote: > > You can hace %{role} in your hierarchy setting in your site.pp: > > $role=hiera('role'

Re: [Puppet Users] Best method to query role specific data when using roles/profiles + hiera as an ENC

I believe I understand 'Data Source Resolution' but it doesn't address our issue unless I'm missing something. The question is how to assign a role to a server so that we can use a new role level in our hierarchy. On Tuesday, September 9, 2014 7:37:51 PM UTC+2, Poil wrote: > > Hi, > > I think

[Puppet Users] What do you use the 'group' attribute for when using the acl module?

The *acl *module has a parameter named '*group*' which takes a list of users, groups or SIDs. What is it for? When would I need it? The documentation is fuzzy. This is what it says: Properties group The entity or entities that have access t

Re: [Puppet Users] Best method to query role specific data when using roles/profiles + hiera as an ENC

You can hace %{role} in your hierarchy setting in your site.pp: $role=hiera('role') Regards El 09/09/2014 11:34, "JeremyCampbell" escribió: > We are implementing the profiles/roles pattern with hiera and using hiera > to assign roles i.e. hiera_include('classes'). Current hierarchy: > > :hiera

Re: [Puppet Users] Best method to query role specific data when using roles/profiles + hiera as an ENC

Hi, I think this is what you want : https://docs.puppetlabs.com/hiera/1/hierarchy.html "Data Source Resolution" We are replacing our ENC with this "full hiera" method Best regards Le 09/09/2014 11:34, JeremyCampbell a écrit : We are implementing the profiles/roles pattern with hiera and usi

Re: [Puppet Users] .fixtures.yml functionality in spec helper

On Sep 8, 2014 2:21 PM, "Brett Swift" wrote: > > why isn't puppetlabs_spec_helper installing dependencies of my dependencies? ... > but puppetlabs_spec_helper doesn't. > > I didn't see a ticket for this ontickets.puppetlabs.com. Is this a feature request, a defect, or pebcak ? Assuming y

[Puppet Users] Announce: Puppet Enterprise 3.3.2 is available

Dear Puppet Enterprise Users, Puppet Enterprise 3.3.2 is now available. This is a security release of Puppet Enterprise. All users of Puppet Enterprise 3.x are encouraged to upgrade when possible to Puppet Enterprise 3.3.2. Puppet Enterprise 3.3.2 includes fixes to address multiple vulnerabiliti

[Puppet Users] Announce: Puppet Enterprise 2.8.8 is available

Dear Puppet Enterprise Users, Puppet Enterprise 2.8.8 is now available. This is a security release of Puppet Enterprise. All users of Puppet Enterprise 2.x who are unable to upgrade to Puppet Enterprise 3.x are strongly encouraged to upgrade when possible to Puppet Enterprise 2.8.8. Puppet Enter

Re: [Puppet Users] Best method to query role specific data when using roles/profiles + hiera as an ENC

On Tue, Sep 09, 2014 at 02:34:52AM -0700, JeremyCampbell wrote: > We are implementing the profiles/roles pattern with hiera and using hiera >to assign roles i.e. hiera_include('classes'). Current hierarchy: > >:hierarchy: >  - "%{clientcert}" >  - "%{environment}" >  - g

[Puppet Users] Type inheritance

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello I just came across an interesting problem with the mount provider. We try to manage NFS mounts on the servers and purge all instances which are not in the catalog. Since the mount type/provider collects all the mounts it would simply destroy t

[Puppet Users] Best method to query role specific data when using roles/profiles + hiera as an ENC

We are implementing the profiles/roles pattern with hiera and using hiera to assign roles i.e. hiera_include('classes'). Current hierarchy: :hierarchy: - "%{clientcert}" - "%{environment}" - global We have several roles which require their own configuration data. e.g. Firewall role, VPN