Option to turn off workspaces

[leg100]

Many users don't use "workspaces", i.e. they just have the default workspace in a root module and that's it. And the tools they use, e.g. terragrunt, assume as much.

Introduce the option to "turn off workspaces":

• Hide workspace listings
• Don't run workspace list automatically
• Hide other workspace commands

[paluszkiewiczB]

Aside of opting-out of workspaces, it would be nice to be able to load .tfvars from custom paths.
Currently for workspace dev, variables are loaded from dev.tfvars.
When workspaces are turned off, there will be no way to pick the .tfvars file, right?

[leg100]

This issue title is a bit of a misnomer; it is impossible to turn off workspaces. Terraform always has at least one workspace named default. In fact you cannot delete or rename the default workspace.

When users say they "don't use workspaces", what they mean is that they only use the default workspace, and don't use any other workspaces named other than default.

With that in mind, if I implemented this feature without changing the variable loading functionality, and you opted to "turn off workspaces", then Pug would load default.tfvars if found.

As for loading variables from custom paths, I'd have to ask what the use case would be for such functionality? You'd have one root module, with one state, but you would want to load one of several custom variables files, which to me seems odd. Whereas it makes sense to have a variables file per workspace, because each workspace has its own state.

[paluszkiewiczB]

You'd have one root module, with one state, but you would want to load one of several custom variables files, which to me seems odd.

Our organisation has an interesting convention of creating var files with the same name as the root module.

So you have apigw/apigw.tfvars and cognito/cognito.tfvars.

I'm aware those could be moved to whatever.auto.tfvars, but our CI is configured to work as described above.

[leg100]

Our organisation has an interesting convention of creating var files with the same name as the root module.

Given terraform already has a built-in method for automatically loading variable files using the *.auto.tfvars naming you mention, I'm not going to alter Pug to suit a particular organization's "interesting convention"!

[paluszkiewiczB]

I do understand your concerns, but I felt like Pug was supposed to be a 'better' way of dealing with terraform CLI.

CLI supports flag -var-file, so I thought it is fairly reasonable to expect the same from Pug? Aside of interesting conventions, this option is available to all the Terraform users and should (?) be expected to be supported.

Otherwise Pug will become an opinionated tool - which is completely fine, but it would be nice to list unsupported native Terraform CLI features in README.

[leg100]

Pug supports all the terraform flags: e.g. .pug --arg -var-file my-var-file.tfvars.

But I think what you're asking for is templating the var file argument, which neither Terraform nor Pug supports.

[paluszkiewiczB]

Oh, that actually suits my use case

Sorry I haven't noticed that 😅

Thank you!