The runtime configuration is an optional setup applied to individual runs instead of being global to the stack. It's defined in
.spacelift/config.yml YAML file at the root of your repository. A single file is used to define settings for all stacks associated with its host Git repository, so the file structure looks like this:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
The top level of the file contains three keys -
version which in practice is currently ignored but may be useful in the future,
stacks containing a mapping of immutable stack id to the stack configuration block and
stack_defaults, containing the defaults common to all stacks using this source code repository. Note that corresponding stack-specific settings will override any stack defaults.
Considering the precedence of settings, below is the order that will be followed, starting from the most important to the least important:
- The configuration for a specified stack defined in config.yml
- The stack configuration set in the Spacelift UI.
- The stack defaults defined config.yml
In cases where there is no stack slug defined in the config, only the first two sources are considered:
- The stack configuration set in the Spacelift UI
- The stack defaults defined in config.yml
Since we adopted everyone's favorite data serialization format, you can use all the YAML shenanigans you can think of - things like anchors and inline JSON can keep your config DRY and neat.
Purpose of runtime configuration»
The whole concept of runtime configuration may initially sound unnecessary, but it ultimately allows flexibility that would otherwise be hard to achieve. In general, its purpose is to preview effects of changes not related to the source code (eg. Terraform or Pulumi version upgrades, variable changes etc.), before they become an established part of your infra.
While stack environment applies both to tracked and non-tracked branches, a runtime configuration change can be pushed to a feature branch, which triggers proposed runs allowing you to preview the changes before they have a chance to affect your state.
If the runtime configuration file is not present or does not contain your stack, default values are used - refer to each setting for its respective default.
Stacks configuration block»
Each collection defaults to an empty array.
These scripts allow customizing the Spacelift workflow - see the relevant documentation here. The following are available:
Defaults to an empty map.
The environment allows you to declaratively pass some environment variables to the runtime configuration of the Stack. In case of a conflict, these variables will override both the ones passed via attached Contexts and those directly set in Stack's environment.
Defaults to an empty string, pointing to the working directory for the run.
Project root is the path of your project directory inside the Hub repository. You can use this setting to point Spacelift to the right place if the repo contains source code for multiple stacks in various folders or serves multiple purposes like those increasingly popular monorepos combining infrastructure definitions with source code, potentially even for multiple applications.
The runner image is the Docker image used to run your workloads. By making it a runtime setting, Spacelift allows testing the image before it modifies your infrastructure.
Defaults to the latest known supported Terraform version.
This setting is only valid on Terraform stacks and specifies the Terraform version that the run will use. The main use case is testing a newer version of Terraform before you use it to change the state since the way back is very hard. This version can only be equal to or higher than the one already used to apply state changes. For more details on Terraform version management, please refer to its dedicated help section.
Pulumi version management is based on Docker images.