Rundeck Job-as-Code Operations Library Prompt
Convert ad-hoc operational scripts into a version-controlled Rundeck job library with input validation, node filtering, and role-based execution controls.
- Target user
- Operations and SRE teams standardizing self-service runbooks
- Difficulty
- Intermediate
- Tools
- Claude, ChatGPT
The prompt
You are a senior operations engineer who turns tribal-knowledge scripts into a governed, version-controlled Rundeck job library. I will provide: - A set of existing manual procedures or shell scripts - The target node inventory and how nodes are tagged - Who is allowed to run what, and any change-window constraints - Whether jobs need approval before executing Your job: 1. **Inventory and triage** — group the procedures into candidate jobs; flag any that are too risky to fully automate yet. 2. **Job definition** — express each as a Rundeck Job YAML/XML with typed options, regex/enum validation, secure options for secrets, and sensible defaults. 3. **Node targeting** — define node filters and `threadcount`/`maxPercentage` so a job cannot fan out beyond a safe blast radius. 4. **Error handling** — add step-level error handlers, keepgoing rules, and a notification on failure. 5. **Access control** — map jobs to ACL policy roles (who can run, who can approve). 6. **Approval and dry-run** — add a manual-approval step or `-dry-run`/no-op option for destructive jobs. 7. **Source control** — describe storing jobs as code with SCM import and a review gate. Output as: (a) the job catalog table, (b) one fully annotated job definition, (c) the ACL policy snippet, (d) a migration plan. Require a dry-run option and an approval gate on any job that restarts, deletes, or modifies production state.
Run this prompt with AI
Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.
Related prompts
-
Event-Driven Automation with StackStorm and Rundeck Prompt
Architect an event-driven automation system where webhooks, alerts, and platform events trigger sensors → rules → actions, with idempotency, deduplication, and safe-by-default execution in StackStorm, Rundeck, or a webhook router.
-
Intelligent Runbook Selection Engine Prompt
Design an AI-assisted layer that maps an incoming alert or incident to the right runbook (or flags that none exists), ranks candidates by signal match, and hands the on-call a confidence-scored shortlist instead of a wiki search.
-
Automation Client-Side Rate Limiter Token Bucket Design Prompt
Design a client-side rate limiter for automation that calls external APIs, using a token-bucket to stay under provider quotas, absorb bursts, and coordinate limits across concurrent workers without tripping 429s.
-
Cross-Region Automation Failover Orchestration Design Prompt
Design the orchestration that fails automation control planes and scheduled jobs over to a secondary region, avoiding split-brain double-execution while guaranteeing critical jobs still run during a regional outage.
More Automation prompts & error guides
Browse every Automation prompt and troubleshooting guide in one place.
Reading prompts? Get all 500 in one free PDF
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.