Issue #7316 has been updated by Daniel Pittman.
eric sorenson wrote: > This bug as it's titled is only half correct; pluginsync turns out to be a > bad way to deliver faces and other complex plugins. Modules are indeed > supported for loading faces, and loading faces from the modulepath works > correctly now. So, to make sure I understand: we can no longer send faces or any other complex plugin to the Puppet agent with PluginSync - instead they need to be shipped as full modules, even though the agent doesn't use them? Is there some documented way to package them so that you don't have to ship a Puppet module, but rather an OS package that you can manage? If not, that is probably going to make our users less unhappy than just disabling the entire feature has. ---------------------------------------- Bug #7316: puppet face applications (subcommands) delivered via pluginsync and as modules should work https://projects.puppetlabs.com/issues/7316#change-71072 Author: Dan Bode Status: Closed Priority: Urgent Assignee: eric sorenson Category: Faces Target version: 3.0.0 Affected Puppet version: Keywords: face faces subcommand application module plugin pluginsync Branch: https://github.com/puppetlabs/puppet/pull/571 If you deliver a new face that consists of: * application * face * action for face via pluginsync, then the application isn't actually found, and worse, it taunts you by showing it to you in the list of available subcommands. -- 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.
