Bug 33396

Summary: FR: file triggers
Product: Sisyphus Reporter: Ivan Zakharyaschev <imz>
Component: puppetAssignee: majioa <majioa>
Status: NEW --- QA Contact: qa-sisyphus
Severity: enhancement    
Priority: P3 CC: 3aHyga, cas, imz, led, majioa, mike, nbr, obirvalger, pav, rider, stalker
Version: unstable   
Hardware: all   
OS: Linux   

Description Ivan Zakharyaschev 2017-04-19 20:09:55 MSK
puppet agent could invoke special file triggers when important files are modified.

For example, I've described one case like this in a manifest:

    file {
      "/etc/resolv.conf":
        ensure  => present,
        content => template('apipkg/dnsmasq/resolv.conf.erb'),
        notify => Exec['update_chrooted']
    }
    exec { 'update_chrooted':
      command     => 'update_chrooted all',
      refreshonly => true,
    }

puppet agent could have had built-in triggers for such files. Perhaps, invoking the triggers from /usr/lib/rpm/*.filetrigger would also make sense.

The tricky thing is to do this not very often and not very late: after a group of files is modified, but before any other action (so that there is no attempt to use the modified files).
Comment 1 Малъ Скрылевъ 2022-09-22 22:44:55 MSK
А можно ли на примере продемонстрировать функциональность?