In regard to: [Puppet Users] Managing untemplatable configuration files,...:
So, does it make sense to store files with host specific configuration in them on the puppet master? Files that are either unable to be turned into templates, or that I don't know enough about the application to make templates. Or is there a better way?
It's not the best way, but if it gets you started on puppet and helps you get to the point where your infrastructure is in a known state, then it's worth doing. It's definitely better than not managing the file content, and remember that that too is an option; you can manage just the permissions and existence, without managing the content itself. Learning puppet is kind of like software development. Some day you'll look back on your "1.0" version and think "what was I thinking?!", but even knowing that's going to happen, you shouldn't get caught up in "paralysis by analysis" at the start. It's good that you want to do things elegantly or "correctly" even starting out, but don't let the lack of a perfect solution keep you from making any progress at all. Start with the simple stuff, like file-shipping entire config files where necessary, but keep learning and keep refining. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, IACC Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 -- 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.
