You can configure the backend for terraform to use with
Below are examples.
You may also be interested in:
When you run
terraspace commands, it will use the files in the
config/terraform folder and builds them with the deployed module. For example, let’s say you have an
├── app │ ├── modules │ │ └── instance │ └── stacks │ └── demo └── config └── terraform └── backend.tf
terraspace up demo
.terraspace-cache/dev/stacks/demo/backend.tf using the
config/terraform/backend.tf. If you want to just build the files without deploying, you can also use
terraspace build. Below are examples of backends.
For variables available see Backend Config Variables
Strip Trailing Behavior
Terraspace expansion will remove the trailing dashes and slashes in case the instance option is at the end and is not set. For example, let’s say
INSTANCE is not set.
Will result in:
us-west-2/dev/demo # notice there's no trailing slash
Why Is Env in Bucket Name?
By default, the bucket name has the ENV at the end. This is done so we can easily see which environment the bucket stores Terraform statefiles for. This quickly helps with debugging. If you prefer not to have the ENV at the end of the bucket name, remove it after generating the project with
terraspace new project.