rundeck-plugins/http-step


Rundeck HTTP Workflow Step Plugin

Download


Step 1. Add the JitPack repository to your build file

Add it in your root settings.gradle at the end of repositories:

	dependencyResolutionManagement {
		repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
		repositories {
			mavenCentral()
			maven { url 'https://jitpack.io' }
		}
	}

Add it in your settings.gradle.kts at the end of repositories:

	dependencyResolutionManagement {
		repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
		repositories {
			mavenCentral()
			maven { url = uri("https://jitpack.io") }
		}
	}

Add to pom.xml

	<repositories>
		<repository>
		    <id>jitpack.io</id>
		    <url>https://jitpack.io</url>
		</repository>
	</repositories>

Add it in your build.sbt at the end of resolvers:

 
    resolvers += "jitpack" at "https://jitpack.io"
        
    

Add it in your project.clj at the end of repositories:

 
    :repositories [["jitpack" "https://jitpack.io"]]
        
    

Step 2. Add the dependency

	dependencies {
		implementation 'com.github.rundeck-plugins:http-step:1.1.8'
	}
	dependencies {
		implementation("com.github.rundeck-plugins:http-step:1.1.8")
	}
	<dependency>
	    <groupId>com.github.rundeck-plugins</groupId>
	    <artifactId>http-step</artifactId>
	    <version>1.1.8</version>
	</dependency>

                            
    libraryDependencies += "com.github.rundeck-plugins" % "http-step" % "1.1.8"
        
        

                            
    :dependencies [[com.github.rundeck-plugins/http-step "1.1.8"]]
        
        

Readme


Rundeck HTTP Workflow Step Plugin

This plugin provides a way to send HTTP requests as part of a Rundeck workflow step. It is somewhat based on https://github.com/rvs-fluid-it/rundeck-httppost-plugin.

Build Status Dependency Status Test Coverage Coverty Scan

Features

  • GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
  • Authentication: BASIC or OAuth 2.0
  • Project or Framework level configuration
  • Support for Self Signed SSL Certificates

Caveats

OAuth 2.0 only supports the Client Credentials Grant Type. The OAuth configuration is per-project or per-framework. This means that each job will share the entire project or entire frameworks credentials. However, this allows those credentials to be externalized into the framework configuration and avoids them being exported with projects.

Todo

  • Support request parameters from config and/or data