You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently this Redshift provider does not allow that. The underlying aws-sdk-go-v2 implicitly uses the environment variable AWS_PROFILE if set.
This means that if you are using AWS profiles, you need to remember to run Terraform with AWS_PROFILE=customprofile terraform plan, or the GetClusterCredentials call will fail. This is pretty cumbersome.
I think it would be a good idea to add a top level configuration option to this Redshift provider, like this:
provider "redshift" {
profile = "customprofile"
}
Implementing it should be pretty straight-forward unless I'm mistaken.
The Terraform aws provider allows setting AWS profile like this:
Currently this Redshift provider does not allow that. The underlying aws-sdk-go-v2 implicitly uses the environment variable
AWS_PROFILE
if set.This means that if you are using AWS profiles, you need to remember to run Terraform with
AWS_PROFILE=customprofile terraform plan
, or theGetClusterCredentials
call will fail. This is pretty cumbersome.I think it would be a good idea to add a top level configuration option to this Redshift provider, like this:
Implementing it should be pretty straight-forward unless I'm mistaken.
The aws-sdk-go-v2 allows specifying a profile explicitly:
The provider schema would need to be expanded with the
profile
option:terraform-provider-redshift/redshift/provider.go
Lines 24 to 26 in bbfe59a
The
redshiftSdkClient
function would need to pass the profile name toLoadDefaultConfig
, if set, or else fall back to calling it as before:terraform-provider-redshift/redshift/provider.go
Lines 234 to 235 in bbfe59a
The text was updated successfully, but these errors were encountered: