v0.19.662
Drift Detection
Drift detection allows you to automatically identify discrepancies between your defined infrastructure and what’s actually running. You can now configure periodic drift detection checks for components and sandboxes through a simple cron schedule.Features
Drift Detection for Sandboxes
You can now define a cron schedule in yoursandbox.toml that periodically checks for drift by performing a “terraform
plan”:
Drift Detection for Components
Similarly, drift detection can be configured at the component level for Terraform, Helm, and Kubernetes Manifest components. Example for a Helm component:Note: Changes to drift_schedule require rebuilding the sandbox or component to take effect.
Drift Visibility
The install components page now clearly highlights components that have drifted from their defined state and provides direct links to the relevant workflows to review the differences.

Limitations
Current Workflow Constraint: At present, only one workflow can run per install at a time. This means:- If a drift detection workflow is running when you attempt to manually deploy a component or reprovision a sandbox, your workflow will be queued until the drift workflow completes.
- We’re actively working to remove this limitation in an upcoming release.
Deny plans and continue workflow
We can now deny plan and continue with the workflow with rest of the component. Deny button comes with additional option to deny and skip steps.
Actions TUI
Actions and Action Runs for installs can now be viewed via the cli.
Nuon Runner Cloudformation Stack
The stack has been updated to remove a policty in order to reduce permissions available to the Runner ASG instances. It is recommended to update the stack to versionv0.1.8.
Bug Fixes and Improvements
- Improvements to generate steps to improve resilience in Temporal.
- Fix to disable server side apply on helm client for components.
- Fix where some Nuon plans can not be generated if outputs are not ready yet.
- Fix where some app configs from older cli versions (pre 0.19.620) would not correctly build.
- Fix where some build runners could run out of memory and not recover.