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

[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/…