-
Notifications
You must be signed in to change notification settings - Fork 825
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
Support custom env variables #221
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
News? |
Any update on this? |
As a workaround (and if you're using fish), you can set an environment variable based on the name of the profile while invoking
Here the name of the profile gets appended to the name of the kubectl config file, so you don't have to update the kubectl config each time a different aws-vault profile is used. |
Looking to see if there's any interest in support custom environment variables, i.e.
FOO=bar
Primary use is for
TF_VAR_foo
. There's a few terraform providers (i.e. Github, etc.) that use user-scoped keys instead of globally scoped keys (global keys could be used inkms
withchamber
or another shared keystore, but the user-scoped keys should probably be kept locally)is there any interest in a feature like this if a pr is made or is
aws-vault
soley going to focus onaws
creds (completely valid as well)? also, thanks for all the great work!The text was updated successfully, but these errors were encountered: