v0.19.539
Workflows UI
The UI view of each step now includes details on the step itself. For instance, you can see details when generating a step.
Workflows are now supported by actions and deploys
Workflow Cancellation
You can now cancel a workflow by clicking the “Cancel” button at the bottom of any running workflow.
This cancellation will make a best effort to cancel the current running step, including cancelling any running jobs on the runner.
Improvements to Action Outputs
Previously, action outputs combined the outputs from all steps into a single dictionary. Now, you can access all outputs by step as well.
Renaming an action step can potentially break references to actions. We plan to add an ID field for output references soon.
Kube Config + Credentials
We now automatically inject a valid kube config into the environment for each action. You can reference theKUBECONFIG
env var to find a configuration file for the install sandbox the runner has access to.
Currently, all actions use the maintenance role defined in your app.
Terraform Workspaces
All sandboxes and terraform components use the Nuon API as their state backend. You can now see resources that are managed via the UI:
backend
configuration for working with the state of an install sandbox or component directly.

If you get a deploy error saying you have two backends configured, please remove your customer backend configuration as the runner environment will automatically configure it
This is controlled with a feature flag and we will be working with users to enable this one-by-one.
Bug Fixes and Internals
- Fixed an issue where the runner could run out of space.
- Fixed an issue where reprovisioning an install could fail if the stack was unable to be templated during initial setup.
- Fixed a bug where all components would rebuild if the previous sync failed.