in openstack_tasks/examples/swift/proxy.pp and openstack_tasks/examples/swift/storage.pp
This manifest snippet makes sure that the directory with concat fragments for rsyncd doesn't get purged on each puppet run. I guess, the bug in concat module should be filed as well.
Is merging swift-proxy and swift-storage tasks is a good thing at all? It seems to make it harder for plugin authors to customize deployment graph.
I'd suggest making something along those lines:
$rsync_conf_name = '/etc/rsyncd.conf' conf_safe_ name = regsubst( $rsync_ conf_name, '[/:]', '_', 'G') /${rsync_ conf_safe_ name}"
$rsync_
$concatdir = $::concat_basedir
$fragdir = "${concatdir}
File <| name == "${fragdir} /fragments" |> {
purge => false,
}
in openstack_ tasks/examples/ swift/proxy. pp and openstack_ tasks/examples/ swift/storage. pp
This manifest snippet makes sure that the directory with concat fragments for rsyncd doesn't get purged on each puppet run. I guess, the bug in concat module should be filed as well.