Sandboxes manage the base layer infrastructure for your application in each customer’s cloud account.
sandbox.toml
file inside the root of your App Config directory.
To configure a Sandbox, specify a repo and the correct parameters for your Sandbox.
Inputs and variables, either inline in the sandbox.toml
or a tfvars
file, can be used to configure the Sandbox, and these are passed to the Terraform code that is run by the Sandbox.
You can configure Sandboxes to use either a public repo (using a public_repo
block) or a private GitHub
repo (using a connected_repo
block). Read more about VCS configuration here.
public_repo
block) or a private GitHub
repo (using a connected_repo
block). Read more about VCS configuration here.
sandbox.toml
.
AWS EKS Sandbox
AWS EKS with Karpenter Sandbox
AWS Min Sandbox
account.region
output from the Sandbox to configure a Helm chart component:
vars
block to your sandbox.toml
file, or a sandbox.tfvars
file in the same directory as your sandbox.toml
. The values in this block will be used as defaults for all installs of this App.:
inputs.toml
file and then reference it in your sandbox.toml
file. In this example, we define a root domain Input and use it to set the public_root_domain
variable in the Sandbox:
sandbox.toml
to point to your new Sandbox code. Custom Sandboxes can also use private GitHub repos, that are connected to Nuon.