Hi Thomas, have you tried the `puppet generate type` workflow described on that doc to avoid the problems with environment bleed-through? You said you failed w/the elasticsearch module and I'm wondering if that is because the `generate` stuff is not working, or whether there's another part of the problem.
On Monday, November 28, 2016 at 10:24:29 AM UTC-8, Thomas Müller wrote: > > > > Am Montag, 28. November 2016 19:06:55 UTC+1 schrieb Rob Nelson: >> >> This will work but I would caution against it. Only recently has per >> environment segregation been implemented and there are still some issues >> present (I believe most fixes showed up in 4.8.0 but not sure). You don't >> want the same module at two different versions for each group being mixed >> and matched improperly. But, it's a judgement call if that's more worrisome >> than an extra PE master. >> > > > I can confirm that the issue with different versions of the same module in > different environments with native ruby types/providers is a real problem. > Just encountered it with the elasticsearch module which we wanted to > upgrade. I utterly failed because new types were added and some types > changed. > > If multiple independent teams are working on the same master you will > likely hit this issue faster than with only one team. > > https://docs.puppet.com/puppet/latest/reference/environment_isolation.html > <https://www.google.com/url?q=https%3A%2F%2Fdocs.puppet.com%2Fpuppet%2Flatest%2Freference%2Fenvironment_isolation.html&sa=D&sntz=1&usg=AFQjCNHjIOc5ij8slTKsOc5-OJLqr-Qfvw> > > > - Thomas > > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0beaf7b8-4218-4de2-9eac-73ff5e597597%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
