Use when creating or editing Nullstone IaC YAML files under `.nullstone/` — adding or wiring apps, datastores, networks, domains, subdomains, ingresses, clusters, cluster-namespaces; setting `vars`, `environment`, `connections`, or `capabilities`; configuring `events`. Triggers on file paths `.nullstone/config.yml`, `.nullstone/{env}.yml`, `.nullstone/previews.yml`, and anything under `.nullstone/stacks/{stack}/`.
80
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
events top-level elementAn event is a way to emit notifications, send webhooks, or trigger tasks as a result of a workspace event.
Events consist of 2 pieces:
When added to an IaC file, these events are registered on the environment where GitOps synchronization is performed. You can find these events in the Nullstone UI by navigating to an environment and switching to the "Events" tab. Events registered through GitOps will be labeled with "Managed By" in the UI which indicates that only that repository can edit/remove the event.
events:
all-deployments:
actions:
- app-deployed
targets:
slack:
channels:
- nullstoneevents:
all-approvals:
actions:
- block-needs-approval
targets:
slack:
channels:
- nullstoneactionsThe actions element allows a developer to select a set of actions that will trigger the event. If not specified, the event will trigger on all actions.
Available Actions:
app-deployed - Occurs when an app deployment finishesapp-first-deployed - Occurs when an app deployment finishes for the first timeblock-launched - Occurs when the infra for a block is initially provisionedblock-updated - Occurs when the infra for a block is updatedblock-destroyed - Occurs when the infra for a block is destroyedblock-needs-approval - Occurs when Nullstone requires approval to complete an infra updateblocksThe blocks element allows a developer to select a set of blocks in the environment that will trigger the event. Each element refers to the block by name. If not specified, the event will trigger on all blocks.
statusesThe statuses element allows a developer to filter to a set of statuses that will trigger the event. If not specified, the event will trigger on all statuses.
Available Statuses:
completed - Occurs when the action succeeded.failed - Occurs when the action failed.cancelled - Occurs when a user or the system cancelled the action.disapproved - Occurs when a user disapproves the action.targetsThe targets element allows a developer to emit a notification, send a webhook, or trigger a task. See event targets for more information.