Rundeck
The robomotion rundeck CLI connects to Rundeck for runbook automation and job execution. It lists projects, executes jobs with parameters, and monitors execution status.
When to use
- Execute Rundeck automation jobs with parameters
- List and manage Rundeck projects
- Monitor job execution status and results
Prerequisites
robomotionCLI installed- Package installed:
robomotion install rundeck - Rundeck URL and API token configured via Robomotion vault
IMPORTANT: Session Mode Required for Multi-Step Operations
Each CLI command runs as a separate process — connection IDs from connect do NOT persist across calls.
You MUST use --session on connect and pass --session-id to all subsequent commands.
Workflow
- Install (once):
robomotion install rundeck - Connect with session:
robomotion rundeck rundeck_connect --session --output json # → {"outClientId":"<client-id>","session_id":"<session-id>"} - Use the returned
client-idandsession-idin all subsequent commands:robomotion rundeck rundeck_run_job --client-id "<client-id>" --job-id <job> --session-id "<session-id>" --output json - Disconnect when done:
robomotion rundeck rundeck_disconnect --client-id "<client-id>" --session-id "<session-id>" --output json
Always append --output json to get structured JSON results.
Commands Reference
robomotion rundeck rundeck_connect --session --output jsonConnects to Rundeck server and returns a client IDrobomotion rundeck rundeck_disconnect --client-id --session-id "<session-id>" --output jsonCloses the Rundeck connection and releases resourcesrobomotion rundeck rundeck_execute_job --client-id --job-id --options --node-filter [--30] --session-id "<session-id>" --output jsonExecutes a Rundeck job by ID with optional arguments and node filterrobomotion rundeck rundeck_get_job_info --client-id --job-id [--30] --session-id "<session-id>" --output jsonRetrieves metadata about a Rundeck job
Environment
- ROBOMOTION_API_TOKEN (if vault credentials are needed)