Jira (PUP-2733) Puppet squats on the PuppetX::Puppetlabs and PuppetX::Puppet namespaces

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: Puppet squats on the PuppetX::Puppetlabs and PuppetX::Puppet namespaces Since I was eager to use the binder more in Puppet 4.0, I wondered how much work it was to move out from the Puppetx namespace and what would be a better organization. I now have this work on a branch (did not take long). We have some bikeshedding to do on the name. I picked the name "Puppet::Spi" (for service programming interface) for where the "extension points" are defined. Using this name, I broke up the (currently) two such extensions "BindingsSchemesHandler", and "SyntaxCheckers" into separate modules. (The next to create is the one for DataInModules, and it seemed prudent to not have all of them in the same file). I also added a Puppet::Spi::Configuration that configures the extension points by registering the names and types with the binder. (This was done in Puppetx earlier). Thus to create a new extension: Add a module under puppet/spi Wire it in Puppet::Spi::Configuration, or delegate to the just created module to do it Use it along the lines in the ExternalSyntaxSupport (which BTW could now be merged into the Puppet::Spi::SyntaxCheckers module) I am not completely happy with the name "spi", but variations of "extension" and "ext" seems to be already spoken for a mean something else. The term "plugin" has history in puppet. I landed on SPI (which in contrast to API is for services being plugged in, not for applications). I thought about using some variation of "service", but thought that may clash with other ideas - it is not really a service API - only defined "extension points". Thoughts? Add Comment   Puppet / PUP-2733 Puppet squats on the PuppetX::Puppetlabs and PuppetX::Puppet namespaces The implementation of the heredoc syntax validators added logic into the PuppetX module, took the names PuppetX::Puppetlabs and PuppetX::Puppet and added an implementation into PuppetX::Puppetlabs for json syntax validation and some interfaces into PuppetX::Puppet. The PuppetX module needs to remain as a convention for code *external* to puppet to have... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.