We use the DSL in production here as well, particularly for getting cluster metadata and configuration out of both AWS tags and Zookeeper. Deprecation would probably keep us from upgrading until we had a DSL with similar capabilities
On Saturday, January 26, 2013 11:06:55 AM UTC-6, Eric Sorenson wrote: > > Sorry Sean, this should have gone out contemporaneously with the release > -- here's the release note that explains the rationale. > > Eric Sorenson - [email protected] <javascript:> > irc.freenode.net #puppet: eric0 > > > ### Ruby DSL Deprecated, new Puppet Ruby DSL removed > > We introduced deprecation warnings for the (not-well-documented, > mostly-unused) Ruby DSL; if you are using the Ruby DSL in production > we want to hear from you to learn what you're doing with it -- please > reply to this message on [email protected] <javascript:>! > > Additionally, after testing the revamped Ruby DSL that was in RC1, > we made the call not to ship it. This was a tough decision, but the > number and severity of issues that came up in exploratory testing > led us to the conclusion that it was not supportable code. Again, > if there are issues you run into with the Puppet DSL that you wanted > to solve with the Ruby DSL, we want to hear about this on the > puppet-dev mailing list. > > > On Jan 26, 2013, at 4:31 AM, Sean Millichamp wrote: > > > I've looked on the mailing lists and don't see any community discussion > or announcement of what is (to me) a major course change in significant > Puppet features, the deprecation of the existing Ruby DSL (expected) and > the decision to not replace it with the new one (not expected): > > https://projects.puppetlabs.com/issues/18876 > > > > Maybe I'm the only one who was looking forward to this, but this has me > pretty disappointed and somewhat concerned that this means a long-term > limitation of the sophistication and expressiveness available to modules. > > > > The ticket has an update by Andrew Parker indicating that Puppet > language is going to be worked on to address the shortcomings which might > cause someone to need to use the Ruby DSL. That's great news, I suppose, > but there is no indication of what Puppet Labs thinks those features are or > when we might see them and the new Ruby DSL felt "right around the corner". > > > > Does anyone from PL want to comment? Personally, I'd love to see a "When > the Puppet DSL has these things fixed / enhanced, we think it will be all > you ever need" list. > > > > Sean > > > > > > -- > > You received this message because you are subscribed to the Google > Groups "Puppet Developers" group. > > To post to this group, send email to > > [email protected]<javascript:>. > > > To unsubscribe from this group, send email to > [email protected] <javascript:>. > > Visit this group at http://groups.google.com/group/puppet-dev?hl=en. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
