Using different providers from aws/gcp/azure and profile question

[riccardo]

Hi, is it possible (or will be) possible to use different providers other than AWS/GCP/Azure ones?
(e.g. like the VSphere one)

Also, when the provider is configured with the profile option in app/provider.tf it is ignored and AWS_PROFILE env var is required to let it work. Is the provider accepting all the standard parameters like in terraform?

Thanks,
Riccardo

[tung]

Currently, VSphere is not supported. Here’s a relevant post https://twitter.com/tongueroo/status/1338148044689211394

Would like to see it added. Will consider PRs. Of course, no sweat either way. Otherwise, will get to it in time

[riccardo]

And about AWS profile variable in AWS provider? is it ignored? is it possible to also use an assume_role parameter?

Thanks

[tung]

Wouldn’t use assume_role at the terraform level because the terraspace build process happens early on. So would assume the role at the AWS config level. Here’s a discussion that is relevant:

Customized layering support?

This is because Terraspace detects info like AWS account early on during the build phase, not during run/apply phase. You can use the standard AWS profile instead of the Terraform role_arn. The AWS profile switches earlier, so the same role and AWS account will be used by both terraspace and terraform. Note, it’s a decent effort for Terraspace to parse for terraform role_arn. Will consider PRs, though. The recommendation is to use ~/.aws currently. Docs: https://docs.aws.amazon.com/cli/latest/…

[riccardo]

The same is true for the other options like the profile name to use?

i tried with a provider.tf like this:
provider “aws” {
region = “eu-central-1”
profile = “test_profile”
}

but it was ignored and required the AWS_PROFILE to be declared as an env var. Is that fixable?