Re: [Puppet Users] the issues with thias/fooacl: filesystem ACL

[Sans]

On Friday, May 20, 2016 at 1:21:24 AM UTC+1, Ken Lareau wrote:
>
>  
> If the file changes, fooacl on its own won't notice the change and won't 
> reset the ACLs.  You need to notify the class to ensure it does catch 
> this.  We have something like this for ours that we put after the fooacl 
> resource:
>
> File[] ~> Class['::fooacl']
>
> Hopefully this helps.
>
>
I have something similar but is it actually directly related to the issue I 
described? I have this: 

concat { "${wp_root}/wp-config.php":
mode=> '0400',
require => Wpcli::Core::Download["download_wordpress_${title}"],
notify  => Class['::fooacl'],
}
 
fooacl::conf { "allow_${wordpress::wp_owner}_wp_config_${title}":
target  => "${wp_root}/wp-config.php",
permissions => [ "user:${wordpress::wp_owner}:r" ],
require => Concat[ "${wp_root}/wp-config.php" ],
}

I cannot figure out if there is fundamentally wrong with this or not. Any 
suggestions?

-San
 

-- 
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/32692633-ebef-4e16-9b12-d6519e7ed063%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] the issues with thias/fooacl: filesystem ACL

[Ken Lareau]

On Thu, May 19, 2016 at 5:04 PM, Sans  wrote:

Hi there,
>
> Is anyone using thias/fooacl
>  module? I use it for
> WordPress, to give www-data read access to wp-config.php and few other
> files. Every time puppet runs, the file becomes unreadable:
>
> # file: wp-config.php
> # owner: root
> # group: root
> user::r--
> user:www-data:r--   #effective:---
> group::---
> mask::---
> other::---
>
> eventually breaking the whole site. Any idea why that's happening? And/or
> how can I fix that? Really appreciate any help on this.
>
>
If the file changes, fooacl on its own won't notice the change and won't
reset the ACLs.  You need to notify the class to ensure it does catch
this.  We have something like this for ours that we put after the fooacl
resource:

File[] ~> Class['::fooacl']

Hopefully this helps.

-- 
Ken Lareau

-- 
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/CALR_H%3DsTpx_SKybUpC1FfkvpMeybONh4tqEoVJ35z_qOuiLDug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] the issues with thias/fooacl: filesystem ACL

[Sans]

Hi there,

Is anyone using thias/fooacl  
module? I use it for WordPress, to give www-data read access to wp-config.php 
and few other files. Every time puppet runs, the file becomes unreadable: 

# file: wp-config.php
# owner: root
# group: root
user::r--
user:www-data:r--   #effective:---
group::---
mask::---
other::---

eventually breaking the whole site. Any idea why that's happening? And/or 
how can I fix that? Really appreciate any help on this.

-San

-- 
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/baa51382-f4a7-42b5-ad76-e5365178b0be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.