-
Notifications
You must be signed in to change notification settings - Fork 227
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
Add AWS_VAULT to prompt - option #349
base: master
Are you sure you want to change the base?
Conversation
is there a way to make it do the right thing with whichever combination of vault and profile a user is currently using, rather than requiring manual configuration? i'm not opposed to a combined "aws" segment, similar to the way we group multiple ruby, python, or node version managers into one segment. |
Haven't looked into that as I'm not using aws-vault. I could only assume the intended behaviour. Like: if the vault env var is present, than the profile should not be shown. If not, show the content of the profile env var? |
To be honest I'm not using either AWS option, so I'd defer what's appropriate to people who do :) |
@bobthecow I merged the two functions, kept both options. But AWS Vault will take precedence, as users of I did stick with the new option |
Hi bob. just wanted to follow up here :) let me know if something is missing. |
@s256 Sorry about the delay! I'm thinking we collapse the two options into single It looks like aws-vault has switched over to |
(i'm happy to make whatever changes are needed, i just want to confirm what works for you!) |
In addition to the AWS_VAULT profile, it's also handy to see the currently active AWS Profile. It's not mutually exclusive.
But not everyone uses
aws-vault
but e.g. granted.dev andassume
. Which only set's the profile and does not useaws-vault
. A dedicated setting can ensure that these two don't clash and are disabled by default