That worked, thanks! I didn't realize "file" was even a valid setting for
ensure.
notice:
/Stage[main]/Zabbix/File[/usr/local/etc/zabbix/zabbix_agentd.conf]/ensure:
defined content as '{md5}6b3491d534f04c4eea426b9cf83e637d'
info: /Stage[main]/Zabbix/File[/usr/local/etc/zabbix/zabbix_agentd.conf
Have you tried explicitly setting the ensure value - a la "ensure => file" - on
the files that might exist as symlinks? I tested this out locally and was able
to get Puppet to overwrite a symlink with a file declaration.
On Monday, January 21, 2013 at 11:31 AM, Sean Kelly wrote:
> I've tried
I've tried that as well. It doesn't work.
On Monday, January 21, 2013 12:34:00 PM UTC-6, Gary Larizza wrote:
>
> You should be able to add "force => true" and get this to work for you
>
> On Monday, January 21, 2013 at 9:19 AM, Sean Kelly wrote:
>
> I am running Puppet 2.7.x (x varies from 14 t
You should be able to add "force => true" and get this to work for you
On Monday, January 21, 2013 at 9:19 AM, Sean Kelly wrote:
> I am running Puppet 2.7.x (x varies from 14 to 20 on different machines). I
> am trying to use Puppet to deploy a new Zabbix agent configuration file. On
> all m
I am running Puppet 2.7.x (x varies from 14 to 20 on different machines).
I am trying to use Puppet to deploy a new Zabbix agent configuration file.
On all machines where the file wasn't a symlink, the deployment worked.
However, every machine where it is a link, Puppet refuses to replace teh