Project_Root Level Runtime Configurations

For repositories that have many Spacelift Stacks associated through usage of multiple project_roots, we have found it’s untenable to utilize the .spacelift/config.yml file. In some of the worst cases there could be 50+ stacks associated for these monolithic repositories.

Runtime configuration - Spacelift Documentation

Currently it appears that only a single runtime configuration is supported at the root of the repository via the .spacelift/config.yml file. Would it be possible to also support a runtime configuration file per project_root that is stored within the stack’s assigned project_root?

As it stands today, we have to make use of globbing via Stack settings - Spacelift Documentation to have updates to .spacelift/config.yml trigger a stack when a value is updated for a CF_PARAM or TF_VAR prefixed variable that the Spacelift run will be relying on. However, including that glob then means every single stack is executed.

The runtime configuration also doesn’t appear to work in a way where if an adjustment is only being made to a single stack in the entire list of stacks in the file, then only that stack needs to be triggered.

In the absence of this working, we’ve opted to force those with these sorts of repos to not use the runtime configuration and instead have to enter everything in through the Spacelift GUI, while we’d prefer this would be part of the same pull request process for other updates to actual template files.