Jira (PUP-6658) Support puppet-REST integration
Title: Message Title Josh Cooper commented on PUP-6658 Re: Support puppet-REST integration This hasn't been updated in years, and we introduced the resource-api as a way to simplify custom providers, so I'm going to close this. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.149299.1472242906000.5254.1583388780084%40Atlassian.JIRA.
Jira (PUP-6658) Support puppet-REST integration
Title: Message Title James Shewey updated an issue Puppet / PUP-6658 Support puppet-REST integration Change By: James Shewey Acceptance Criteria: A scheduler would need to be used to do one URL very every 60 seconds or so over a 90 minute window. If all the URLs were called at once, this could overload the CPU of an a web site or device. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6658) Support puppet-REST integration
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-6658 Support puppet-REST integration Change By: Maggie Dreyer Labels: needs_decision triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6658) Support puppet-REST integration
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6658 Support puppet-REST integration Change By: Henrik Lindberg Component/s: Puppet Server Component/s: Types and Providers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6658) Support puppet-REST integration
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6658 Support puppet-REST integration Change By: Karen Van der Veer Scrum Team: Puppet Server Modules Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6658) Support puppet-REST integration
Title: Message Title
James Shewey commented on PUP-6658
Re: Support puppet-REST integration
Actually, I find that per-api modules are very *in*convenient for a few reasons reasons. First, they require the author of the module to re-solve the problem of how to talk to the REST interface every single time a new module is written. Secondly, if someone has not authored a module already, then I can either give up or try to engineer my own. This leaves me with the standard puppet resources, or I must write my own ruby module. If I want to make that idempotent, it makes it even more complicated. So here's what that looks like using the existing puppet resources for foreman:
exec
{
"/bin/curl -s -k --user '${user}:${password}' --request POST -H 'Content-Type: application/json' --data '{\"compute_attribute\":{
\"vm_attrs\":{
\"cpus\":\"2\",
\"corespersocket\":\"1\",
\"memory_mb\":\"1024\",
\"cluster\":\"Dev-Test\",
Jira (PUP-6658) Support puppet-REST integration
Title: Message Title Kylo Ginsberg commented on PUP-6658 Re: Support puppet-REST integration If I'm understanding this proposal correctly: offhand, my reaction to this is that per-API modules (as exist today for a number of devices / services) is a great convenience for infrastructure developers. It allows the module developer to define a puppet-y API to the device/service in question, and insulate module consumers from some of the nitty-gritty of a given API. If there were "one module to rule them all", my concern would be that we'd be pushing complexity up to the module consumers and that puppet manifests would become correspondingly more complex or unwieldy. On a related note though, it might be worth taking a look at https://github.com/garethr/garethr-kubernetes, which uses swagger to auto-generate much of the code for a puppet module. But that's just me. James Shewey: you might want to float this idea on the puppet-users google group to get exposed to a broader range of feedback on the idea. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6658) Support puppet-REST integration
Title: Message Title James Shewey updated an issue Puppet / PUP-6658 Support puppet-REST integration Change By: James Shewey I would like the ability to manage configurations via REST calls. Often times, web sites and appliances can be configured via REST APIs. Examples include:ConfluenceThe ForemanF5 BIG-IP Load BalancersMany moreManaging configurations of these via cURL calls using BASH's curl is tedious. Furthermore, This is not idempotent. I can set something, but if it is changed, there is no way to set it back without some serious gymnastics. This feature request is to have an agent periodically poll RESTful URLs and compare their settings to those defined in a puppet module or manifest directly (rather than having to BASH hack using exec calls to /bin/curl).To do this, puppet would need to know about the REST structure of a given resource. Fortunately, there are emerging standards for documenting REST APIs such as swagger and Hydra:http://stackoverflow.com/questions/4937379/example-of-a-well-documented-restful-servicehttp://stackoverflow.com/questions/28242676/what-specification-should-i-use-for-documenting-rest-apisSimilar to an SNMP MIB, documents describing the API could be fed to puppet and then puppet could idempotently manage the configuration of a wide variety of RESTful devices. Instead of having to develop a module for every single RESTful device or software, one module could rule them all and the requirement for providing the instructions for interfacing with that device or software would be on the design team of the software or appliance. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6658) Support puppet-REST integration
Title: Message Title James Shewey created an issue Puppet / PUP-6658 Support puppet-REST integration Issue Type: New Feature Affects Versions: PUP 4.6.1 Assignee: Unassigned Components: Puppet Server Created: 2016/08/26 1:21 PM Environment: Web Priority: Normal Reporter: James Shewey I would like the ability to manage configurations via REST calls. Often times, web sites and appliances can be configured via REST APIs. Examples include: Confluence The Foreman F5 BIG-IP Load Balancers Many more Managing configurations of these via cURL calls using BASH's curl is tedious. Furthermore, This is not idempotent. I can set something, but if it is changed, there is no way to set it back without some serious gymnastics. This feature request is to have an agent periodically poll RESTful URLs and compare their settings to those defined in a puppet module or manifest directly (rather than having to BASH hack using exec calls to
