Issue #16401 has been updated by Daniel Pittman. Assignee deleted (Daniel Pittman)
eric sorenson wrote: > (Assigning for the moment to Daniel as a proxy for Mateusz) > Daniel do you know whether this is possible in the rewritten ruby dsl? I don't, I am afraid, know the answer to this. I don't believe I saw specific evidence either way in the tests, and I have not checked. It would not be unreasonably hard to take the approach of having a method akin to `type(...)` to create defines inside a namespace, however, or to have some block-based approach to Puppet level namespace management, if this is not already done. ---------------------------------------- Feature #16401: make it possible to namespace ruby-defined types https://projects.puppetlabs.com/issues/16401#change-72735 Author: Chris Price Status: Investigating Priority: Normal Assignee: Category: language Target version: Affected Puppet version: Keywords: Branch: When working on a module that contains a mix of types that are defined via puppet manifests and via ruby code, it would be really nice for all of the types to be namespaced the same way for the end user. So, e.g., when working on the puppetdb module, I am going to end up with one type defined a manifest that the user will access as: puppetdb::foo and another one that is defined via ruby that they will access as: puppetdb_bar That's a bummer as far as UX goes, but I don't think it's currently possible to get the "::"'s into the name or namespace of a ruby-defined type. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
