002 - Install Inputs, dependencies, and more
Install Inputs, dependencies and more
May 6th, 2025
Input Types
You can now define an input type, which denotes which type of input is accepted. This is used to control rendering across different install inputs and will allow us to build more semantic meaning into inputs.
You can define a type
field on an input in your config. The following types are supported:
string
bool
number
json
list
Input types are currently only settable as metadata, but will be rolled out to all different surfaces of install management soon.
string
as their type
.Internal Inputs
Internal inputs are inputs that are only settable via the Nuon dashboard. This allows you to define inputs that a customer cannot control directly or set internal values.
You can use internal: true
to mark an input as internal.
internal: false
.Dependencies
Dependencies are now auto-configured based on the variables that you define. For example, the following config would mark container_image
as a dependency.
If you would like to manually declare a dependency, you can define it in a component config using:
Terraform Component KUBECONFIG
Each terraform component run will now have a KUBECONFIG
env-var with the path to the kubeconfig for the run.
You can use the kubectl
provider without any additional configuration, as the file and env var are exposed using defaults:
Terraform Workspace Improvements
You can now see resources managed by a Terraform component in the UI.
To make working with terraform state easier, you can now download a nuon backend config file for any workspace with the push of a button.
Bug Fixes and Improvements
- Fixed an issue where only 64MB was reserved for the runner.
- Input Group and Input ordering is now respected.
- Fixed an internal issue where dependencies were not configured with an app-version, but only used the latest.
- Missing or circular dependencies will now error when syncing a config.