Open
Description
Describe the Bug
When using a notify
meta parameter in a concat::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:
service { 'foo':
ensure => 'running',
}
concat { '/tmp/foo':
ensure => 'present',
}
concat::fragment { '/tmp/foo bar':
target => '/tmp/foo',
content => 'bar',
order => '10',
notify => Service['foo'],
}
- Make sure service
foo
is running - Make sure file
/tmp/foo
is not present - Run
puppet apply
on the above code
Notice: Compiled catalog for localhost in environment production in 0.08 seconds
Notice: /Stage[main]/Main/Concat[/tmp/foo]/File[/tmp/foo]/ensure: defined content as '{sha256}fcde2b2edba56bf408601fb721fe9b5c338d10ee429ea04fae5511b68fbf8fb9'
Notice: Applied catalog in 0.03 seconds
As you can see, even though the file changed, it didn't trigger restart of the service.
Environment
- Version 6.2.0
- Platform Debian 11.4