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
Would really love to see this too as it would make it easier for multiple team members to run Terraform without having to modify this path to suit their home directory. For now, perhaps using the AWS_SHARED_CREDENTIALS_FILE environment variable is the best way to go.
pathexpand(string) - Returns a filepath string with ~ expanded to the home directory. Note: This will create a plan diff between two different hosts, unless the filepaths are the same.
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 11, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
aws
provider does not expand the user's home directory~/
for theshared_credentials_file
argument. See below:provider "aws" { shared_credentials_file = "~/.aws/credentials" profile = "Profile" region = "${var.region}" }
Error message:
No valid credential sources found for AWS Provider.
Please note that and error does not occur when supplying the full path instead of ~/.
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
This appears to have happened in the past as well: - GH-3856
The text was updated successfully, but these errors were encountered: