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
- Running database migrations
- Executing maintenance scripts
- Collecting diagnostic information
- Automating operational tasks
- Running custom health checks
How do you configure an Action?
Create anactions
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:
We maintain a collection of commonly-used actions in an open-source repo for you to get started with.
Running Actions
Actions can be triggered in several ways:- Manually via the Dashboard or CLI
- On a schedule
- In response to events