-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Honor $AWS_CONFIG_FILE
env variable
#540
Comments
This sounds like a good idea! |
Another question: is this mapping of roles to config files static or dynamic? Ie: is this something you want to manage outside of aws-sso (managing this environment variable to change where the same roles get written to) or something you really want to set & forget (adding this to the aws-sso config file). |
You're probably correct regarding the credentials-file, I just mentioned it since I set that along with the config-var. I handle this using direnv today so in each of my client-directories I have a .envrc-file which defines where the AWS-tooling should look for config and credentials. I actually already added the |
$AWS_CONFIG_FILE
env variable
So looking at the code... it should work today? I just tested with What version of aws-sso are you using? |
Hmmm, config-profiles seems to do the correct thing. When I just ran aws-sso config it asked if it should update ~/.aws/config though. |
Even more strange. In one of my client directories config-profiles did this:
Maybe my aws-sso config was strange there. I think I've already set that up earlier. Will try in another directory. |
Another client was fine so probably something strange in my config |
Aaah, I had enabled AutoConfigCheck in that config. That seems to want to update the default path always. |
Awesome. that helps a lot. |
- AutoConfigCheck workflow now looks at the AWS_CONFIG_FILE env var - `config-profiles` now offers an explict flag - Refactor code Fixes: #540
- AutoConfigCheck workflow now looks at the AWS_CONFIG_FILE env var - `config-profiles` now offers an explict flag - Refactor code Fixes: #540
Is your feature request related to a problem? Please describe.
I'm working for multiple clients and have split my AWS configuration in different directories by help of direnv and setting the env-vars AWS_CONFIG_FILE/AWS_SHARED_CREDENTIALS_FILE to point at a directory specific for each client. aws-sso seems to ignore those and always updates ~/.aws/config.
Describe the solution you'd like
A possibility to handle config per client somehow
The text was updated successfully, but these errors were encountered: