RUNBOOKS
Create parameterized templates for common operations, store them in Git, and let your team execute with validated inputs. Every run passes through guardrails, masking, and approval workflows automatically.
HOW IT WORKS
Four steps from SQL file to validated, audited, production-safe operation.
Write a runbook template with placeholders for parameters. Use Go template syntax with built-in validation functions.
Commit templates to your Git repository. Hoop syncs automatically. Version control, code review, and branch protection apply.
Point Hoop to your repository with one CLI command or through the web UI. SSH key or token authentication.
Users select the runbook, fill in parameters through a validated form, and run. Guardrails, masking, and audit apply automatically.
Full lifecycle in action
TEMPLATE SYNTAX
Parameters use {{ .parameter_name }} syntax. Chain functions with pipes for validation, type hints, and safe quoting.
Parameter Functions
descriptionHelp text for the inputdescription "Customer ID"requiredError message if emptyrequired "This field is required"defaultDefault value if not provideddefault "US"typeInput type for UItype "number"patternRegex validationpattern "^[0-9]+$"optionsDropdown optionsoptions "active" "inactive"squoteWrap value in single quotessquotedquoteWrap value in double quotesdquoteasenvPass as environment variableasenv "DB_PASSWORD"Input Types
textStandard text inputnumberNumeric inputemailEmail validationdateDate pickertimeTime pickerselectDropdown (use with options)File Extensions
.runbook.sqlSQL queries.runbook.shBash scripts.runbook.pyPython scripts.runbook.rbRuby scriptsLive preview
Template on the left, validated form on the right. Parameters update in real time.
EXAMPLES
PARALLEL EXECUTION
Execute the same runbook across multiple databases, clusters, or environments in parallel. One click. Full audit trail for each.
SECURITY
Input Validation
Use pattern to enforce regex on every parameter. Only numeric IDs, valid emails, or your custom format. Injection attempts rejected before execution.
Environment Variables
Use asenv to pass sensitive values as environment variables instead of inline. Passwords never appear in command strings or session logs.
Safe Quoting
squote and dquote properly escape and quote string values, preventing SQL injection in parameterized templates.
INTEGRATIONS
WHO USES RUNBOOKS
A DBA creates the template once. Support, SREs, and on-call engineers execute with validated inputs. Every run recorded, every parameter logged, every result masked.
ORGANIZATIONAL IMPACT
Every runbook execution generates an auditable event chain. Your compliance team gets continuous evidence that controls are not just defined but actively enforced across your infrastructure.
Connect your Git repository and give your team validated, audited templates in under 10 minutes.