Open faxm0dem opened 2 years ago
looks like this could be the same issue as MODULES-7533 (also see #430)
For some reason these meta parameters are explicitly not copied here: https://github.com/puppetlabs/puppetlabs-concat/blob/4148c4b21d84a4663d291d17700ac6063e678c8c/lib/puppet/type/concat_file.rb#L344
It was introduced in https://github.com/puppetlabs/puppetlabs-concat/commit/dd88b1a4eee853cfff60b99096c05ce85a9d556e but it doesn't explain why those were excluded.
IMHO, one should use concat's resource notify, not an single fragment - result is the same, isn't it?
I can imagine cases where one fragment should notify the service, but not another. For instance, a changed comment in a config file shouldn't restart the service.
IMHO, one should use concat's resource notify, not an single fragment - result is the same, isn't it?
A real world example we have for this is the puppet.conf file on the puppetserver. most changes to this file are only read by the agent and dont require any notify. however changes to the server
section require the puppetserver to be reloaded
Describe the Bug
When using a
notify
meta parameter in aconcat::fragment
, the target resource doesn't get notified.Expected Behavior
When a
concat::fragment
's state changes, it should properly notify the target resource.Steps to Reproduce
Example code:
foo
is running/tmp/foo
is not presentpuppet apply
on the above codeAs you can see, even though the file changed, it didn't trigger restart of the service.
Environment