> On Oct 18, 2015, at 4:37 PM, Trevor Vaughan <tvaug...@onyxpoint.com> wrote: > > Reading the doc again, it seems to be (sort of) already named tk_auth::rule > or trapperkeeper_auth::rule. > > I'm OK with whatever as long as it's namespaced. > > However, given that lots of people probably have a 'puppet' namespace, you > might need another one so that you don't conflict with other people's > existing code. > > I called mine 'pupmod' since it felt like 'puppet' might be reserved at some > time in the future. >
After the comment thread in the doc last wee, top-line module is now `puppet_authorization` and the defined type to manage rules is `puppet_authorization::rule` so I think we should be clear of namespace conflicts. Eric Sorenson - eric.soren...@puppetlabs.com <mailto:eric.soren...@puppetlabs.com> - freenode #puppet: eric0 puppet platform // coffee // techno // bicycles -- 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 puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/3FD69842-405E-4CBC-A158-1FAFFEAD8E6D%40puppetlabs.com. For more options, visit https://groups.google.com/d/optout.
