Configuring Action Workflows
Action workflows can be configured in your app’s TOML config. For example, to define an HTTP healthcheck:Timeout
Each workflow must have a timeout limiting how long it can run. The maxiumum allowed timeout is 30 minutes. Timeouts must be provided as valid Golang time.Duration strings. The example workflow will timeoute after 15 seconds, more than enough time to make a simple HTTP request.Action Triggers
Action triggers are now available for all workflows. You can now use the following set of triggers:pre-provisionpost-provisionpre-reprovisionpost-reprovisionpre-deprovisionpost-deprovisionpre-deploy-all-componentspost-deploy-all-componentspre-teardown-all-componentspost-teardown-all-componentspre-deprovision-sandboxpost-deprovision-sandboxpre-reprovision-sandboxpost-reprovision-sandboxpre-update-inputspost-update-inputspre-secrets-syncpost-secrets-sync
pre-provision or pre-reprovision that include a stack-run,
the trigger will be called right after the runner is healthy.
The following triggers require a component_name field to be set, as they are
tied to a specific component:
pre-deploy-componentpost-deploy-componentpost-teardown-componentpre-teardown-component
pre-component-deploy and post-component-deploy have been renamed to
pre-deploy-component and post-deploy-component for consistency with other
triggers. pre-sandbox-run and post-sandbox-run have been deprecated, in
favor of pre|post-reprovision, pre|post-provision, and
pre|post-deprovisionactions/<action-name>.toml
Steps
Each step in an action requires a command to be run. You can optionally load a script from a repo and provide env vars to configure the environment the command will run in. The example action is pretty simple, so it has only one step. It loads a curl script from our open-source repo of commonly-used scripts, and sets a few env vars to configure it.actions/<action-name>.toml