Custom Scripts in QuickInfra: Automate Any Ops Task Without Building a Pipeline

CI/CD pipelines are great for application deployments. But infrastructure management involves a lot of tasks that don't map cleanly to a deployment workflow: running a database migration before a deploy, executing a maintenance script on a specific instance, clearing a cache, rotating a credential, triggering an ad-hoc health check. QuickInfra's Custom Scripts feature handles all of this.

What Is a Custom Script?

A Custom Script in QuickInfra is a shell script (Bash by default) that you write and store in the platform. It can be run manually on demand from the console, triggered on a schedule, attached as a step in a CI/CD pipeline, or called via the QuickInfra API. The script runs on a target — either an existing VM instance in your cloud account or an ephemeral compute instance spun up for the duration of the script.

Writing a Script

Go to Manage → Custom Scripts → New Script. Give it a name, write your shell script in the editor, set the target type (specific instance or ephemeral), and configure environment variables. QuickInfra's editor has syntax highlighting and a validation pass that catches common issues before you run anything. Scripts are version-controlled — every save creates a new version and you can roll back to any previous version.

Environment Variables and Secrets

Scripts often need credentials or configuration values. QuickInfra lets you define environment variables at the script level — values are encrypted at rest and injected as environment variables at runtime. They never appear in logs, never get committed to a repo, and never live in plain text on the target instance.

Script Templates

The QuickInfra template library includes pre-built script templates for common ops tasks: EC2 instance health check, disk cleanup, log rotation, RDS snapshot trigger, S3 bucket sync, Nginx config reload, and more. Start from a template and customise it for your environment rather than writing from scratch every time.

Scheduling

Scripts can be scheduled using cron-style syntax. A nightly database backup script, a weekly log archive, a daily cost report — configure the schedule in the console and the platform handles execution, logs the output, and sends an alert if the script exits with a non-zero status. No crontab on a server, no lost outputs, no silent failures.

Attaching Scripts to Pipelines

Custom Scripts can be attached to any stage of a CI/CD Pipeline project. A pre-deploy script might run database migrations. A post-deploy script might warm the cache, run smoke tests, or notify an external monitoring system. This turns a standalone script into a reusable pipeline component — write it once, attach it anywhere.