Add support for reading global configuration files

[dcl]

Add support for reading global configuration files

[warrensbox]

Let's say you have multiple projects with different terraform versions for each project, you can specify each terraform version in it's local/current directory.

.
├── terraform-project-1
│   └── version-tf-11.13
├── terraform-project-2
│   └── version-tf-11.14
└── terraform-project-3
    └── version-tf-12.24

If you want ~/.tfswitch.toml in the home directory ~, how do you manage the different versions of terraform for each project?
Are you only using one terraform version for all your project(s)?
@odbaeu @dcl can you please provide more information?

[odbaeu]

Thank you so much for your quick reaction!

I try to keep most of my terraform projects on one version. That's why I think this is a good feature request. But I absolutely agree that it is best practice to have one .tfswitch.toml in each terraform project. This helps other team members to use the correct terraform version.

But back to the feature request: Let’s say I have the following structure:

~/.tfswitch.toml
~/projects/A
~/projects/B
~/projects/B/.tfswitch.toml
~/projects/C

In case the project has a .tfswitch.toml in the project’s directory, this should be picked. If it's not there, tfswitch would look for ~/.tfswitch.toml. In this case ~/.tfswitch.toml would be valid for project A and C.

This also means that ~/.tfswitch.toml is the default configuration and I can overwrite it.

[jurrehart]

I would expand on that and would like to see the following path for version identification stopping at the first match

1. look for required_version in the .TF files
2. look for .tfswitch.toml in current work directory
3. look for .tfswitch.toml in users home directory

[fdamstra]

I would add that if you're doing hierarchical modules, it would be really nice for it to search parent directories. My company's code is organized in terragrunt fashion, like:

~/projects/A
~/projects/A/prod
~/projects/A/prod/vpcs
~/projects/A/prod/instances
~/projects/A/test/vpcs
~/projects/A/test/instances

And then repeat for project B and so forth. It would be extremely useful to look for the .tfswitch.toml in the present directory, then work up the parent directories until either we're in ~ or /.

This would let me use a new version of tf in test while retaining the known-good version in prod, but not have to have dozens (no exageration) of hidden .tfswitch.toml files lying around.

[warrensbox]

will release soon with : #113

[odbaeu]

.tfswitch.toml from the local directory should have a higher priority than ~/.tfswitch.toml.