> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nuon.co/llms.txt
> Use this file to discover all available pages before exploring further.

# 038 - Spacelift install stacks and CLI automation

> Provision install stacks through Spacelift, get improved error messages, and drive the nuon CLI reliably from CI/CD.

*July 10, 2026*

## Provision install stacks with Spacelift

You can now provision and manage Nuon install stacks through [Spacelift](https://spacelift.io) instead of applying the
stack's Terraform yourself — letting Spacelift handle state, run history, and drift for the install stack. It currently
supports GCP, with AWS support planned. A new guide walks through both the blueprint and Terraform provisioning paths.

* Generate and apply install stacks through Spacelift.
* New [Provision stacks with Spacelift](/guides/provision-stacks-with-spacelift) guide.
* Install stacks now use a dedicated Terraform provider.

## Improved error messages

Component deploy errors are now parsed and surfaced directly in the UI, classified by failure type. When a Helm or
Terraform deploy fails, the workflow shows a specific reason, making it faster to tell a transient error from a real
misconfiguration.

<div
  style={{
backgroundImage: 'url(https://mintcdn.com/nuoninc/rwkI-PuH3GKcdjG2/images/changelog/038-bg.png?fit=max&auto=format&n=rwkI-PuH3GKcdjG2&q=85&s=1457c11a65c5029980de23e5a0d6602a)',
backgroundSize: 'cover',
backgroundPosition: 'center',
padding: '48px 24px',
borderRadius: '12px',
display: 'flex',
justifyContent: 'center',
margin: '24px 0'
}}
>
  <img
    src="https://mintcdn.com/nuoninc/rwkI-PuH3GKcdjG2/images/changelog/038-classified-errors.png?fit=max&auto=format&n=rwkI-PuH3GKcdjG2&q=85&s=24965ab0bfd8cb9514d8225539af591f"
    alt="A classified deploy failure in the Nuon dashboard: 'Terraform could not acquire the state lock', with how-to-fix steps and the raw output"
    style={{
  width: '100%',
  maxWidth: '820px',
  borderRadius: '8px',
  boxShadow: '0 20px 60px rgba(0,0,0,0.4)'
}}
    width="2550"
    height="1220"
    data-path="images/changelog/038-classified-errors.png"
  />
</div>

## Custom label colors

Labels can now be assigned custom colors, making apps, installs, and components easier to scan and group. Set them in your app config's `label_colors` map or from the dashboard — see [label colors](/guides/managing-apps#label-colors).

<div style={{ display: 'flex', justifyContent: 'center', margin: '24px 0' }}>
  <video
    src="https://mintcdn.com/nuoninc/rwkI-PuH3GKcdjG2/images/changelog/038-label-colors.mp4?fit=max&auto=format&n=rwkI-PuH3GKcdjG2&q=85&s=9fd8925e4299795292f047ee02e75048"
    autoPlay
    loop
    muted
    playsInline
    style={{
  width: '100%',
  maxWidth: '820px',
  borderRadius: '12px',
  boxShadow: '0 20px 60px rgba(0,0,0,0.4)'
}}
    data-path="images/changelog/038-label-colors.mp4"
  />
</div>

## Dashboard improvements

* Better table support when rendering Markdown content, including HTML tables in READMEs.
* Compact workflow step design with corrected timestamps and links.
* "Forget component" is now always available.
* Orphaned install actions, runbooks, and components are filtered out of pickers.

## Improved headless CLI experience

Fixes that make the `nuon` CLI more reliable when you drive it headlessly from CI/CD:

* **`nuon apps sync` now uses distinct exit codes**, so CI can separate a sync failure from a build failure:
  * `0` — config synced and all builds succeeded.
  * `1` — sync failed.
  * `3` — config synced, but one or more scheduled component builds failed or timed out.
  * Pass `--no-wait` to skip the build wait so the exit code reflects the sync alone.
* **Config schemas are now satisfiable**, so you can validate app config against them in CI or an editor. Previously the typed schemas (`container-image`, `helm`, `kubernetes-manifest`, and the rest) could never validate any document.
* **Each config file type now has its own schema endpoint** — `GET /v1/general/config-schema/{type}`:
  * Fetch a single type directly, e.g. `/config-schema/helm` or `/config-schema/sandbox`.
  * Each type's schema carries its own `$id`, so editors and validators that cache schemas by URL resolve every config type distinctly instead of collapsing them onto one entry.
  * The older single-URL form still works for backward compatibility: `config-schema?type=helm`, with `?source=` accepted as a deprecated alias that returns a deprecation header instead of an HTTP 400.