Actions
Automate operational tasks and workflows in installs.
Actions allow you to create automated workflows that can be run in Installs. Actions are useful for debugging, running scripts, and implementing health checks.
What are Actions?
Actions are reusable workflows that can be configured to run on your Installs. Each Action consists of:
- A trigger that determines when the action runs
- One or more steps that define what the action does
Actions can be used for:
- Running database migrations
- Executing maintenance scripts
- Collecting diagnostic information
- Automating operational tasks
- Running custom health checks
How do you configure an Action?
Create an actions
directory at the root of the App Config, and create a TOML file for each action. e.g., alb_healthcheck.toml
deployment_restart.toml
kubectl_logs.toml
.
If Actions need to connect to a VCS, use either a public repo (using a public_repo
block) or a private GitHub
repo (using a connected_repo
block). Read more about VCS configuration here.
For example, to pull logs from all Kubernetes pods in a namespace, you would write an action like this:
For example, if you wanted to implement a healthcheck for an AWS ALB, you would write something like this:
Running Actions
Actions can be triggered in several ways:
- Manually via the Dashboard or CLI
- On a schedule
- In response to events
To run an action manually:
Action Triggers
Action Triggers are documented in the Changelog 009.
Action History
You can view the history of action runs using the CLI:
Or get details about a specific run:
Action Permissions
Actions are run with the same permissions as the Runner in each install.