TF_VAR_
they are used in Terraform to use environment variables as Terraform input variables.TF_VAR_
environment variables and mounted files should cover all use cases without the need to introduce an extra entity.<computed>
, which means that their value is only computed at runtime. These are not directly set on the stack but come from various integrations - for example, AWS credentials (AWS_ACCESS_KEY_ID
and friends) are set by the AWS integration and SPACELIFT_API_TOKEN
is injected into each run to serve a number of purposes.GITHUB_TOKEN
environment variable used by the GitHub Terraform provider variable split into two separate environment variables:KUBECONFIG
variable pointing to the actual config file which needs to be present in your workspace as well./
characters in the file path to nest it deeper in directory tree - for example a/b/c/d/e.json
is a perfectly valid file path./mnt/workspace/
, which also serves as a root for all the mounted files. /mnt/workspace/source/
, which also serves as the working directory for your project, unless explicitly overridden by the project root configuration setting (either on the stack level or on in the runtime configuration)./mnt/workspace/source/
as well and it's a legitimate use case, for example, to dynamically inject backend settings or even add extra infra definitions. Just beware of path clashes as mounted files will override your project source code in case of conflict. Sometimes this is what you want, sometimes not.