On 6/28/2010 5:33 PM, Mohamed Lrhazi wrote:
However, I *strongly* urge you to tell us what you problem is
I have a bunch of files that were deployed via kickstart and manual
provisioning procedures that I am "translating" to Puppet...
My condolences.
This one file, /etc/ldap.conf, is deployed from kickstart, but then
later, a manual run of a script by an admin, as part of later
provisioning step, updates ldap.conf with bind password... I need
/etc/ldap.conf deployed right after initial install, and maintained...
but don't want the bindpassword overwritten once it has been updated,
the password is unique to each host.... What would be the right way to
maintain such a file?
Maintain the lists of passwords on the master and provision them using
extlookup and a template. You can still provision a basic ldap.conf on
kickstart, but as soon as puppet kicks in, you'll be in total and
perpetual control of the file.
Best Regards, David
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
--
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.
