Jira (PUP-1876) 3.4.3 broke the ability to add provider-specific parameters to built-in types
Title: Message Title Anthony Ryan commented on an issue Re: 3.4.3 broke the ability to add provider-specific parameters to built-in types Sorry about the late follow up. I had been implementing provider specific options in this way. As of 3.5.0 there is now the package_settings attribute which I am using instead. Add Comment Puppet / PUP-1876 3.4.3 broke the ability to add provider-specific parameters to built-in types Until 3.4.3 it has been possible to extend built-in types as desired in PUP-1183 by including a lib/puppet/type/package.rb file that expands upon the one included in puppet itself. This allowed provider specific options without using install_options. An example of how this worked previously, it was possible to copy lib/puppet/type/package.rb from pu... 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.
Jira (PUP-1876) 3.4.3 broke the ability to add provider-specific parameters to built-in types
Title: Message Title Andy Parker updated an issue Puppet / PUP-1876 3.4.3 broke the ability to add provider-specific parameters to built-in types Change By: Andy Parker Component/s: TypesandProviders Add Comment 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.
Jira (PUP-1876) 3.4.3 broke the ability to add provider-specific parameters to built-in types
Title: Message Title Andy Parker assigned an issue to Anthony Ryan Anthony Ryan, thanks for letting us know about this. This isn't really a use case that we try to support, but I don't think there is anything that we did to specifically prevent it. Could you provide as much detail as possible to cover: What you are trying to do including the changes to the package.rb file that you are making. How this used to work. I suppose that it just worked', but knowing any corner cases you were already aware of would be good. What is now happening. For this, please include any --debug and --trace output that you can. Also, including any extra information about variations and how it behaves is really useful. Puppet / PUP-1876 3.4.3 broke the ability to add provider-specific parameters to built-in types Change By: Andy Parker Assignee: AnthonyRyan Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1876) 3.4.3 broke the ability to add provider-specific parameters to built-in types
Title: Message Title Anthony Ryan created an issue Puppet / PUP-1876 3.4.3 broke the ability to add provider-specific parameters to built-in types Issue Type: Bug Affects Versions: 3.4.3 Assignee: Unassigned Created: 06/Mar/14 1:34 AM Priority: Normal Reporter: Anthony Ryan Until 3.4.3 it has been possible to extend built-in types as desired in PUP-1183 by including a lib/puppet/type/package.rb file that expands upon the one included in puppet itself. This allowed provider specific options without using install_options. An example of how this worked previously, it was possible to copy lib/puppet/type/package.rb from puppet into a module as described in http://docs.puppetlabs.com/guides/plugins_in_modules.html and then modifying that file adding parameters as necessary. Add Comment
