Automate tasks
On the Automation page, review pipelines, monitor jobs, and manage hooks to run routine tasks automatically.
Automation features require the Operator or Admin role.
Open the Automation page
In the sidebar, select Automation.
Create a pipeline
Create Pipeline is a planned feature currently in progress.
The Create Pipeline button is in the upper-right corner of the Automation page. Pipelines are defined in YAML and run automatically when triggered.
A pipeline has three main sections: trigger, steps, and conditions. The Pipeline Configuration (YAML) panel on the page shows an example.
name: Weekly fleet health check
trigger:
schedule: "0 9 * * 1" # Every Monday at 09:00
steps:
- action: scan
target: all_systems
- action: notify
channel: slack
message: "Weekly fleet scan complete. Review results in NimbusWiz."
conditions:
on_failure: notify_admin
CI/CD Pipelines
The CI/CD Pipelines section lists every pipeline configured in NimbusWiz. Each card shows:
| Field | Description |
|---|---|
| Name | The pipeline name |
| Status | Active or paused |
| Trigger type | Manual, Scheduled, or Event |
| Last run | How long ago the pipeline last ran |
| Success rate | The percentage of runs that completed without errors |
| Total runs | The total number of times the pipeline has run |
Each card has three icon buttons: Run, Pause, and Configure.
Pipeline Visualization
The Pipeline Visualization section shows the standard pipeline execution sequence as a flow diagram. The stages are: Trigger, Prepare, Execute, Test, and Deploy. The diagram illustrates the architecture every pipeline follows.
Scheduled Jobs
Creating scheduled jobs is planned.
The Scheduled Jobs section lists every job configured to run on a recurring schedule. Each row shows:
| Field | Description |
|---|---|
| Name | The job name. |
| Schedule | The cron expression that defines the recurrence |
| Next run | The date and time of the next scheduled execution |
| Status | Enabled or disabled |
Event Hooks
Event hook creation is a planned feature currently in progress.
Event hooks trigger an action when a specific event occurs—for example, alerting the on-call team when stability drops below a threshold.
Event hooks are similar to webhooks, but they run inside NimbusWiz instead of sending payloads to an external URL.
The Event Hooks section lists every configured hook. Each card shows the event name, the action it triggers, and a toggle to enable or disable the hook.
Available events
The following events are available.
| Event | Triggered when |
|---|---|
| System Health Critical | A system's health metrics fall into the critical range |
| Deployment Completed | A deployment finishes successfully |
| New Security Patch Available | NimbusWiz detects a new security patch for a registered system |
| Stability Below Threshold | A system's stability score drops below the configured threshold |
Pipeline Configuration (YAML)
The Pipeline Configuration (YAML) section shows the raw YAML for the selected pipeline in a read-only code panel. The YAML defines the pipeline's trigger conditions, steps, and notification rules. Use it to review the configuration of an existing pipeline.
Recent Pipeline Runs
The Recent Pipeline Runs section lists the most recent pipeline executions. Each row shows:
| Field | Description |
|---|---|
| Pipeline | The name of the pipeline that ran |
| Status | Success or failed |
| Duration | How long the run took |
| Time | How long ago the run occurred |