Very cool.
We have extremely heavy audit requirements so this will help.
I like the idea that it is noted and extractable and recordable and
countable for analytics.
Now, if I could only get Puppet to tell me exactly what CLI it would
propose running...
As I don't want to have to massage YAM
On Monday, December 9, 2013 5:12:42 PM UTC-6, Stuart Cracraft wrote:
>
>
> Assume the following question is in regards to Puppet 3.3.2.
>
> So my question is in relation to audit.
>
> file { '/some/random/path/through/the/tree/to/a/file':
> owner => 'luke',
> group => 'rebelalliance',
> mo
Thanks for your comment, I posted a new bug and will wait for a reply from guys.
2010/12/6 jcbollinger :
>
> On Dec 5, 3:19 am, Paul Johnson wrote:
>> sorry, forgot to mention that the target file (/tmp/bar) exists and it
>> shouldn't be optional. I tried adding 'ensure => file' as you guys
>> su
On Dec 5, 3:19 am, Paul Johnson wrote:
> sorry, forgot to mention that the target file (/tmp/bar) exists and it
> shouldn't be optional. I tried adding 'ensure => file' as you guys
> suggested but without luck, it still produces the same error. As to
> reporting this as a bug, there is an officia
sorry, forgot to mention that the target file (/tmp/bar) exists and it
shouldn't be optional. I tried adding 'ensure => file' as you guys
suggested but without luck, it still produces the same error. As to
reporting this as a bug, there is an official bug
(http://projects.puppetlabs.com/issues/5065
On Dec 2, 10:13 pm, Paul Johnson wrote:
> file { "/tmp/bar": audit => content } exec { '/usr/bin/true':
> refreshonly => true, subscribe => File['/tmp/bar'] }
>
> and it produces this error every time:
>
> err: /Stage[main]//Node[localhost]/File[/tmp/bar]: Could not evaluate:
> Could not retriev
