Issue #3692 has been reported by Alan Barrett.
----------------------------------------
Feature #3692: config_version remains unchanged when files are changed
http://projects.puppetlabs.com/issues/3692
Author: Alan Barrett
Status: Unreviewed
Priority: Normal
Assigned to:
Category:
Target version:
Affected version: 0.25.4
Keywords:
Branch:
When puppet manifests are edited, puppetmasterd usually notices, and computes a
new configuration version by invoking the "config_version" script or by using
the default (derived from the current time). However, when files are edited,
the configuration version remains unchanged.
<pre>
# .../modules/mymodule/manifests/init.pp
class mymodule {
file { "/dir/filename":
ensure => file,
source => "puppet:///mymodule/filename",
}
}
</pre>
If I edit .../modules/mymodule/manifests/init.pp, then the configuration
version gets updated next time a client connects. So far so good.
However, if I edit .../modules/mymodule/files/filename, the configuration
version remains unchanged. A message on the client say "info: Applying
configuration version '<old version number here>'".
>From my point of view, I would like it to be seen as as a configuration change
>when I edit a file that gets deployed from a "files" subdirectory in a module.
> I use subversion revision numbers in the config_version, and I want to be
>able to tell people "check that the configuration version is at least <N>, to
>be sure that you have the latest changes to <filename>".
--
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 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-bugs?hl=en.
