On Jun 28, 2010, at 8:33 AM, Mohamed Lrhazi wrote:
> Thanks a lot Daniel.
>
>> However, I *strongly* urge you to tell us what you problem is
>
> Right, am newbie here, so am sure am doing a lot of things wrong, or
> thinking about them from a wrong way....
>
> I have a bunch of files that were deployed via kickstart and manual
> provisioning procedures that I am "translating" to Puppet...
>
> 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?
You might want to look into Augeas. That would allow you to manage some
settings in the file, but not all the settings. This way you can change any
settings you want even after the password is set.
Here's an example.
augeas { "set_ldap_settings":
#If your ldap.conf is directly in etc, you'll need to change the next
line
context => "/files/etc/ldap/ldap.conf",
changes => [
"set SIZELIMIT 11",
"set BASE dc=exaple,dc=com",
"set URI 'ldap://ldap.exaple.com
ldap://ldap-master.exaple.com:666'"
},
}
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
