On Thursday, August 16, 2012 3:26:23 AM UTC-5, Daniele Sluijters wrote: > > Hi, > > We've ran into the same problem. Our current solution, which we're not > happy about, is to also have the custom types on the master/production > environment. Doing that at least the custom types are always available. > Unfortunately, it makes it impossible to deploy an update of a custom type > to a branch/environment for testing. >
For what it's worth, I would recommend using an entirely separate Puppet process for testing. If you like, it can run on the same server, but a different port. That would have several advantages for you, among them - you would be able to test modifications to your Puppet extensions without putting them into production - you would be able to test how changes apply to and affect your various environments (or if you use environments only for this purpose, then you could drop them altogether) - your production master would not be exposed to any unproven code - it would fit in more intuitively (to me) with source control, branches, etc. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/-fzqCwR2PNAJ. 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.
