http://groups.google.com/group/puppet-users/msg/817d8af153f504a4
Recap is below for those of you jumping in late:
Can we fix this in the code?
Can we identify cases where "!ruby/sym absent" was written out, and
not fire an event when we update from that to a new value?
Recap:
On 2.6.5, we are auditing by default for all source managed files.
If you were on 2.6.4 (and probably earlier) and
if you managed a file with the source parameter and
if the local file was absent or content differed, we wrote out:
!ruby/sym type: !ruby/sym absent
!ruby/sym owner: !ruby/sym absent
to state.yaml, even if you weren't auditing.
Also, if you managed a file recursively with source, we also wrote out:
!ruby/sym content: !ruby/sym absent
As of 2.6.5, when auditing all attributes,
we write out the correct value:
!ruby/sym type: file
!ruby/sym owner: 1000
!ruby/sym content:
This is a value change for the attribute being audited, and will
thus send appropriate events.
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
