New Rundeck HTTP Plugin

[Ilya Kogan]

Hello,

As part of Ohio University's efforts to deploy Rundeck in our infrastructure, we've developed a Rundeck plugin to send HTTP requests that has support for:

- GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS methods

- HTTP BASIC or OAuth 2.0 authentication

- Support for Self Signed SSL Certificates

- Project or Framework level configuration

The plugin is available at https://github.com/ohioit/rundeck-http-plugin. We're deploying our first production use of the plugin this weekend and I'd love to contribute it back to the community in whatever form.

[Alex Honor]

Hi Ilya,

Thanks for your contribution. I added the project to the list.

http://rundeck.org/plugins/2016/06/16/http-workflow-step.html

--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/7e228528-f273-4379-9b8d-1bb951c56012%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alex Honor

[SimplifyOps, Inc | a...@simplifyops.com ]

Be sure to comment and vote on Rundeck Feature Development!

[Niall Munnelly]

Maybe this is obvious to developers, but how and where are the authentication details defined? As variables in framework or project.properties? How are they invoked?

There's a paucity of practical information in the documentation; I'd love an alternative to executing curl commands in my plugin's payload and was pretty stoked to see this, but I don't see what it's bringing to the table just yet. Who here's put this plugin through its paces?