I'm currently trying to do a basic set of infrastructure on 3 different projects via terraform cloud.
I have 3 workspaces:
- development
- staging
- production
with their own variables defined for service accounts and all of that.
I want -- for the time being at least -- to interact with the infrastructure via CLI from my local machine. The issue is I have to define the workspace in mybackend as a hardcoded string so I can't put in a variable.
I found a clever way around it using dev.hcl files which contain data about the backend so I can simply run:
terraform -chdir=infrastructure init -backend-config="dev.hcl"
It works but it is quite a lot to type whenever I want to run init/plan/apply so I'm looking for a simpler way to streamline this.
I've tried creating scripts in the root package.json and dynamically change dev to an argument passed to the CLI, unfortunately this doesn't work consistently across windows and linux and because of the order of commands needs to be exact with terraform CLI, I'm out of options.
The current scripts I have in package.json:
"tf-init-dev": "terraform -chdir=infrastructure init -backend-config=\"dev.hcl\"",
"tf-plan-dev": "terraform -chdir=infrastructure plan -backend-config=\"dev.hcl\"",
"tf-apply-dev": "terraform -chdir=infrastructure apply -backend-config=\"dev.hcl\"",
"tf-init-stage": "terraform -chdir=infrastructure init -backend-config=\"stage.hcl\"",
"tf-plan-stage": "terraform -chdir=infrastructure plan -backend-config=\"stage.hcl\"",
"tf-apply-stage": "terraform -chdir=infrastructure apply -backend-config=\"stage.hcl\"",
"tf-init-prod": "terraform -chdir=infrastructure init -backend-config=\"prod.hcl\"",
"tf-plan-prod": "terraform -chdir=infrastructure plan -backend-config=\"prod.hcl\"",
"tf-apply-prod": "terraform -chdir=infrastructure apply -backend-config=\"prod.hcl\"",
and I imagine I'll be adding more commonly used ones as the project develops.
Is there a better way of tackling this use case?