May 19th, 2025

​

Improved Secrets

The secrets have had their naming convention updated to better support multiple deployments into the same account and faciliate access to these names which are guaranteed to be unique. The new naming convention is:

{{.nuon.install.id}}/{{.secret.name}}

Additionally, the secret ARN is now included in the secrets objects in {{.nuon.secrets}}.

​

Handle Expired Stacks

CloudFormation stacks have an expiration of 24 hours when setting up a customer install. If a stack is not run in 24 hours, it will show a better error message.

​

Retry Failed Workflow

You can now retry a workflow from where it failed by clicking the “Retry Workflow From This Step”. This will create a new workflow that starts at the step that was failed.

​

View Deploy Plan

You can now view a deploy plan, from the UI:

​

Nuon Helm driver

You can now store helm release information in Nuon API. You can customise it by editing the helm_driver value in runner.toml file of the app.

runner_type = "aws"
helm_driver = "nuon"

​

Helm Driver Options

• secret- Store helm release information in kubernetes secrets. This is the default driver.
• configmap- Store helm release information in kubernetes configmaps.
• nuon- Store helm release information in Nuon API.

​

Internal Migrations

We have been rolling out the following internal, platform improvements:

​

Nested Event Loops

Each Nuon app and install is backed by a long lived Temporal workflow called an eventloop. Event loops are used for orchestration, control-flow and limit concurrency.

Previously, each install had a single event loop meaning only a single deploy or job could be executed at once. We have updated the install to have an event loop for each component, action, and the sandbox. This is a future migration that will allow us to build parallel deploys based on the component graph, and more.

​

Component Builds

As part of now building Nuon BYOC, we have deprecated an internal service, and changed the way we build components.

​

Fixes

• Deprovisioning an install now works when outputs are missing. Previously, a failed deprovision could leave an install in an undeprovisionable state.
• Deprovisioning an install uses the previous active deploy config.
• Fixed a bug where some outputs were not showing in the state.
• Fixed a bug where the permissions boundary was not set properly on the stack.
• Fixed a bug where a required secret was not required in the CloudFormation stack config.