On Tuesday, December 4, 2012 9:25:04 PM UTC-6, Navid Paya wrote: > > OK, that makes sense. Thanks for the tip. Gotta go do some reading. The > thing is this very same manifest used to work under puppet 2.6. >
No, I'm sure it didn't. None of the relevant characteristics of Puppet have changed between 2.6 and 3.0. I don't doubt that you have a real-world manifest that broke between 2.6 and 3.0, but it's not because Puppet ever auto-included nested classes. If I were to take a wild guess, I'd say it's far more likely that your failure is related to the removal of dynamic scoping (which was discussed a lot around here, and for which the entire Puppet 2.7 series produces deprecation warnings). You can see a full list of changes from the 2.x series to the 3.0 series in the Puppet 3 release notes: http://docs.puppetlabs.com/puppet/3/reference/release_notes.html. Honestly, there is very little in the backwards incompatibility list that pertains to the Puppet language, and all changes of that type involve features that were already deprecated in the previous release series. 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/-/2Sat3nPs7lkJ. 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.
