Rundeck for Rancher

This plugin is based on "kallqvist/rundeck-rancher" work.

The goal here is to create a rundeck plugin able to :

Run with rundeck directly (running, or not, in a container).
Using Rancher Rest-API and websockets to execute bash commands in already running containers (as returned by ResourceModelSource plugin).
Run command into container even if tty is activated.
Connect a job to several rancher environments
Trigger a "start-once" container
Send/Run file/script into container

Getting started

Tested on Rundeck 2.6.11-1
Config and API keys specific to your Rancher installation.
/bin/sh need to be present in the container.
Python 2
Some python librairies installed on your rundeck server :
websocket-client (>=0.37.0)
requests (>=2.12.4)
python-dateutil (>=2.5.3)
(something like : apt-get install python-websocket python-requests python-dateutil)

or build it (bash & zip needed)

Clone this reposiroty
Run scripts/build-all.sh (need zip in your PATH)
Copy the file target/rancher-plugin.zip to your rundeck serveur at $RDECK_BASE/libext/.

add a new Resource Model Source in your projet configuration :
(You need to adapte the source number "1" according to your project) configuration
resources.source.1.type=rancher-resources
The rancher-plugin resources model definition.
resources.source.1.config.cattle_access_key=0123456789AABBCCDDEE
Your acces key to connect to the rancher API
resources.source.1.config.cattle_config_url=https\://myrancher.home/v1
Mind the "" before ":"
You can use API v1 or v2-beta
resources.source.1.config.cattle_secret_key=azertyuiopqsdfghjklmwxcvbn123456798000
Your secret key to connect to the rancher API
resources.source.1.config.environments_ids=1a11029,1a11070,1a11082
Your different environments IDs to search in (comma separated).
resources.source.1.config.limit_one_container=false
Only retrieve one container from earch environment ID.
resources.source.1.config.stack_filter=my_super_stack
Restrict containers discovery to a specific stack.
Configure a new Node Executor method :
(You need to specify the accound used by the plugin to connect and run command through rancher's API)
project.plugin.NodeExecutor.rancher-executor.cattle_access_key=0987654321EECCDDBBAA
Your acces key to connect to the rancher API. Same or different as the resources source
project.plugin.NodeExecutor.rancher-executor.cattle_secret_key=gAbmufoxW753PktyqKbcs4gjUMfJWRK4YYzwXLso
Your secret key to connect to the rancher API. Same or different as the resources source

Add a step Command to your workflow.
Specify you command as usual (ex: /bin/ls /tmp)
It's something good to filter nodes with properties like : type: container, state: running and even environment_name: something
if needed, you can add 2 options to your job definition :
retry_attemp (default 5)
How many times rundeck should check if your command have finished.
retry_interval (default 30)
How long should rundeck wait between each check (in second).

Your command will be sent to the container, when rundeck will check until it finishes.

At the end, you will get a log containing all stdout and stderr at once.
All stderr intries are prefixed with "ERROR - ".

The exit code of your command will be send to rundeck.

Providers for "node-executor" and "file-copier" are stored in the node attributes.