I am looking to see if I can make this work with a define or have to resort to an each loop. Still hacking away to see what I can find. With the each I can still loop through to try to get to the goal of having a key/value pair to pass on to a template only if the current client matches one of the host names in scope.
Worst case I will just go ahead to split the variables up accordingly per client and hard code in the module / parms file. My goal was to have it so we could just use the CSV file we were given to dynamically build the data. But it may be less costly (from a CPU cycle level) to just go back to the good old days :) On Sunday, January 22, 2017 at 10:56:46 PM UTC-5, John Gelnaw wrote: > > On Friday, January 20, 2017 at 12:28:02 PM UTC-5, James Perry wrote: >> >> Thanks. >> >> The reason I have a CSV is that is what is provided from the users out of >> their own private database where they keep this data. I have to take the >> detail as it is given. Now I can manually process the data to be how I >> think I want, but I'm trying to keep this as simple as possible for the >> other team members (KISS principal). >> >> For the custom ENC, the new environment is Foreman over top of Puppet. >> Can I use a Puppet ENC when Foreman is setup to do that itself? >> > > I have a very complex ENC myself, so the idea of merging the Foreman ENC > with my own ENC appeals to me-- Ultimately, they're both just spitting out > YAML. > > My current line of attack is to have my ENC (configured already within > puppet) call the Foreman node.rb script, merge the two data structures and > output the resulting YAML, but the migration to puppet 4.x has priority at > the moment. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/2c504b24-599a-4251-bcbf-25c8fbf75377%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
