Yeah it depends on what you need to do. I would hope the vendor also exposes a CLI that talks to their REST API, so you could call to that without needing a module, but if a module makes sense and one is built, this is something we could possibly consider for core inclusion.
The uri module is quite useful for some simple things, though registering a lot of results and using a lot of conditionals quickly gets into programming territory -- which is to say a module could be used, or even the script module could be used to call a small script too. On Thu, Apr 10, 2014 at 2:05 PM, Paul Durivage <[email protected]>wrote: > Hi Drew, > > You're right, the URI module is available. I didn't mention it because > Salman mention he was going to be coordinating the automation for an entire > cluster. The URI module is useful, yes, but interacting with a large API > for complex tasks? That's what I meant when I said that I don't want to > know what such a playbook might look like. > > So, yes, that functionality exists, but it's way less than ideal for > working repeatedly with complex APIs. This functionality really deserves > to be in a module. > > > On Thu, Apr 10, 2014 at 1:37 PM, Drew Northup <[email protected]>wrote: > >> On Thursday, April 10, 2014 12:14:24 PM UTC-4, Paul Durivage wrote: >>> >>> The type of work you're looking to do is best handled by writing a >>> Cloudera module. I don't want to imagine how one might wrap a REST API in >>> a playbook -- that does not sound fun or reasonable. :) >>> >> >> Paul, >> It has already been done... >> >> On Wed, Apr 9, 2014 at 2:11 PM, Salman Haq <[email protected]>wrote: >>> >>>> I am exploring automation of a Hadoop cluster. >>>> >>>> The vendor (Cloudera) requires that all configuration happen through a >>>> REST API. See [1] for Cloudera Python API client. >>>> >>>> My question is: Is there a prior example of an Ansible playbook that >>>> wraps an HTTP api? >>>> >>> >> Salman, >> Look at this module's doc page: http://docs.ansible.com/uri_module.html >> (Romeo even provided some examples, prior to the existence of a JIRA >> module). >> >> >>> >>>> Thanks! >>>> Salman >>>> >>>> [1] http://cloudera.github.io/cm_api/docs/python-client/ >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ansible-project/48e32f14-a034-43ca-ad22-7758f5a5a28d%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/48e32f14-a034-43ca-ad22-7758f5a5a28d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CAK6JQEF3R5-oY8mSPvnZBeTr38hZbKLuJz%3DT%3DHB24bCaFzK9qQ%40mail.gmail.com<https://groups.google.com/d/msgid/ansible-project/CAK6JQEF3R5-oY8mSPvnZBeTr38hZbKLuJz%3DT%3DHB24bCaFzK9qQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgxZx%3DoZv2MQ%2BG18r0%3D93cby8bYKCb2HwpGgs9ObFzRQ0A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
