Issue #22221 has been reported by Zachary Stern.
----------------------------------------
Feature #22221: File resources being audited for content should honor the
backup parameter.
https://projects.puppetlabs.com/issues/22221
* Author: Zachary Stern
* Status: Unreviewed
* Priority: Normal
* Assignee:
* Category:
* Target version:
* Affected Puppet version:
* Keywords: customer
* Branch:
----------------------------------------
Currently, if you have a file resource that is audit only, and you are auditing
it for content without managing that content, it will not be filebucketed when
the content changes.
This doesn't makes sense, because clearly if you are auditing a file for
content, you care about what that content is. Therefore, when that content
changes, we should probably filebucket the file.
#####To reproduce:#####
In site.pp:
# /etc/puppet/manifests/site.pp
filebucket { 'main':
path => false,
server => 'puppet.example.com',
}
File { backup => main, }
file { '/tmp/foo.txt':
ensure => file,
audit => 'content',
}
>From command line:
# puppet agent --test
# echo 'foobarbaz' > /tmp/foo.txt
# puppet agent --test
Output will note that audit for content sees a change, but will not backup file
to filebucket.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.