On Wed, Jan 25, 2012 at 10:57 AM, Throwe, Jesse <je...@throwe.com> wrote: > Having just gone through this conversion recently, it's not as hard as it > seems. > > - Puppet variables are managed through the puppetVar entries for the > objectClass so theres no need to extend the schema. > - All variables are passed to the manifests as a string. You need to > identify your hashes in your manifests and split them over a > delimiter. > - No parametrized classes (as of 2.6.x) can be called directly from > LDAP. We had to locate our paramterized classes that were impacted and > convert them over to using variables, and throwing a parse error if > required variables were not located. This took maybe an hour to do. > - At least as of 2.6.x it appears that the environment variable is > completely ignored from the client. This behavior is actually desired > but if you have gotten used to --environment=newfeatureenv it can be a > change. > > We are also leveraging dynamic environments as described in > http://puppetlabs.com/blog/git-workflow-and-puppet-environments/ which > helps separate development from production. >
Thank you for the details. I will keep these points in mind while I test the LDAP ENC. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
