gschueler

Use of remoteUrl and editUrl attributes for Node resources

Nodes defined in resources.xml can use editUrl and remoteUrl to specify that the node entry should be edited via some remote URL. The URLs can specify properties about the node to expand prior to being loaded, which allows you to e.g. submit query parameters using the node name.

editUrl - specifies a URL to a standalone remote site which will allow editing of the Node. When specified, the Node resource will display an "Edit" link in the Rundeck GUI and clicking it will open a new browser page for the URL.

remoteUrl - specifies a URL for a remote site which will be loaded in an iframe within a Rundeck page. Clicking the "Edit" link for the Node will load content from the site within the current Rundeck page, allow you to perform your edit at the remote site, and has optional hooks to report the state of the editing process back to the Rundeck page for a more streamlined user inter

gschueler

diff --git a/core/src/java/com/dtolabs/rundeck/core/authorization/providers/Policies.java b/core/src/java/com/dtolabs/rundeck/core/authorization/providers/Policies.java
index bbe8b2b..7979ab0 100644
--- a/core/src/java/com/dtolabs/rundeck/core/authorization/providers/Policies.java
+++ b/core/src/java/com/dtolabs/rundeck/core/authorization/providers/Policies.java
@@ -16,50 +16,22 @@
 
 package com.dtolabs.rundeck.core.authorization.providers;
 
-import java.io.File;
-import java.io.FileNotFoundException;

gschueler

Configuring Rundeck for SSL

This document describes how to configure Rundeck for SSL/HTTPS support, and assumes you are using the rundeck-launcher standalone launcher.

Before beginning, do a first-run of the launcher, as it will create the base directory for Rundeck and generate configuration files.

1. cd $RDECK_BASE; java -jar rundeck-launcher-1.0.0.jar

This will start the server and generate necessary config files. Press control-c to shut down the server.

gschueler

RunDeck REST API

Proposal.

API requests

path: /api/

Requests are made to the RunDeck server URL under the /api/ path. This path doesn't require the normal authentication to the server, but requires that a valid API Key be provided with each request. If one is not provided, then a response of 403: Unauthorized will be returned.

gschueler

feature branch changes

git checkout development # load development branch
git pull origin # synch with remote
git checkout -b myfeature # create new feature branch and check out
# commit changes
git checkout development # go back to development
git pull origin # see if any changes from upstream

gschueler

        RED="\[\033[0;31m\]"
     YELLOW="\[\033[0;33m\]"
      GREEN="\[\033[0;32m\]"
       BLUE="\[\033[0;34m\]"
  LIGHT_RED="\[\033[1;31m\]"
LIGHT_GREEN="\[\033[1;32m\]"
      WHITE="\[\033[1;37m\]"
 LIGHT_GRAY="\[\033[0;37m\]"
 COLOR_NONE="\[\e[0m\]"

gschueler

Run a Job using Curl

This document describes how to use CURL to interact with the RunDeck server to invoke a Job to run.

The steps are as follows:

1. Authenticate to the RunDeck server and acquire a session cookie.
2. Submit run request for particular Job ID, sending session cookie.

gschueler

Run a Job using Curl

This document describes how to use CURL to interact with the RunDeck server to invoke a Job to run.

The steps are as follows:

1. Authenticate to the RunDeck server and acquire a session cookie.
2. Submit run request for particular Job ID, sending session cookie.

gschueler

#!/bin/bash

#usage: runjob.sh <server URL> <job ID>

errorMsg() {
   echo "$*" 1>&2
}

DIR=$(cd `dirname $0` && pwd)

gschueler

#!/bin/bash

#usage: rdjobslist.sh <server URL> <project> [output.xml]

errorMsg() {
   echo "$*" 1>&2
}

DIR=$(cd `dirname $0` && pwd)