Mohamed Lrhazi <lrh...@gmail.com> writes:
> How do I deploy a file, but then stop deploying it when it has been changed
> in a certain way?
Don't do that. That way lies madness. You will have machines that are
randomly in and out of the pool of managed files all over the place, with no
way to audit or manage that.
Instead, only include the "file" define on machines where you do want to
manage the content, or do something like this:
file { "/etc/ldap.conf.puppet": ... }
exec { "/bin/ln -s /etc/ldap.conf.puppet /etc/ldap.conf":
creates => "/etc/ldap.conf"
}
That way you will only put the puppet file in place (by creating the symlink)
until something exists in that location. Refining this (eg: dealing with
pre-existing files) is easy enough to extend it to.
However, I *strongly* urge you to tell us what you problem is — because you
are clearly wanting to do this to solve some problem, and there might be a
much better way to do what you want.
Regards,
Daniel
--
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
