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
I am thinking it would be nice to implement shared_config_file in the aws provider stanza in the same way shared_credentials_file is already implemented. The primary use case of this that I envision would be to dynamically fetch the default region (if set) for whatever profile is in use.
So for example, instead of something like this:
provider "aws" {
shared_credentials_file = "${pathexpand("~/.aws/credentials")}"
region = "${var.region}"
}
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am thinking it would be nice to implement
shared_config_file
in the aws provider stanza in the same wayshared_credentials_file
is already implemented. The primary use case of this that I envision would be to dynamically fetch the default region (if set) for whatever profile is in use.So for example, instead of something like this:
...it would instead be possible to do this:
The text was updated successfully, but these errors were encountered: