Issue #7474 has been updated by Daniel Pittman.
Mo Morsi wrote: > Yes, and would still be interested in getting this in. Additionally we've > made some additions to this module upstream that I'll submit / update this > ticket when I have the cycles. They are largely simple extensions to the > current resource type / provider, no major architectural changes, so any new > comments/feedback to the existing submission should still apply. Hey Mo. Sorry this slipped. Part of the reason for the new [development process][1] is to stop things like this being missed. So, I took a brief look at the code, and getting that into core as it stands is going to be hard: it depends on two external gems, curb, and nokogiri. The later has C components, making it a heavy dependency. If we were to make this part of the core we would really like to eliminate both of those dependencies out in favour of things in core like `Net::HTTP` and all. (Which is more ugly, and means more code, indeed.) However, we are trying to encourage people to use [the module forge][2] for extensions like this now. That has a bunch of advantages, and most of them are for you. The signal advantage is that if you ship as part of Puppet core you will be tied directly to our stability promises and release cycle. You can't possibly add features - or even fix bugs - with less than a couple of weeks delay, and more often several months. (...and, then, no body in the world will get those for anything up to three years - until distributions update their release of Puppet!) On the forge you can release on your own schedule, and everyone gets a better experience. You should be able to do everything in a module that you could do in core, and it should work everywhere - including agents that were released before we merged this. Would you be willing to go down that route? [1]: github.com/puppetlabs/puppet/tree/master/CONTRIBUTING.md [2]: http://forge.puppetlabs.com/ ---------------------------------------- Feature #7474: puppet web resource type / provider https://projects.puppetlabs.com/issues/7474#change-55389 Author: Mo Morsi Status: In Topic Branch Pending Review Priority: Normal Assignee: Daniel Pittman Category: newfeature Target version: Affected Puppet version: Keywords: puppet, web, resource, provider, type Branch: http://groups.google.com/group/puppet-dev/browse_thread/thread/b163ae7f6b96965e As part of the aeolus project (http://aeolusproject.org) we provide a puppet recipe to install and configure the different components that make up the framework. Several of our components primarily provide web interfaces which to configure the components and to create data, and previously we were manually 'exec'ing the curl command to invoke those requests. The problem with this is that its tricky to both verify the HTTP response code as well as parse / verify the contents of the response, so to assist with this we wrote a generic web resource type and provider (based on libcurl) to perform the actual operation. There is nothing aeolus-specific as part of this resource / provider, so I'm sharing it here with the hopes of getting some feedback and possibly for inclusion in the upstream project. The patch itself can be found here: http://git.fedorahosted.org/git/?p=aeolus/configure.git;a=commitdiff;h=24765b6d92496f6127a903c1c59e3eaf578f30a9 http://mo.morsi.org/blog/node/336 Thoughts? Any way this could be included as part of puppet? -- 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.
