aws-vault: Ubuntu: The collection "aws-vault" does not exist. Please add a key first
I added the env var AWS_VAULT_BACKEND as shown in https://github.com/99designs/aws-vault/blob/master/USAGE.md
The ran aws-vault add account-name. Ubuntu prompted for my password. Then got Added credentials to profile "account-name" in vault
Then trying to use aws-vault fails with The collection "aws-vault" does not exist. Please add a key first
aws-vault --debug ls shows this:
2018/01/18 16:46:34 [keyring] Considering backends: [secret-service]
2018/01/18 16:46:34 Loading config file /home/sebastian/.aws/config
2018/01/18 16:46:34 Parsing config file /home/sebastian/.aws/config
aws-vault: error: The collection "aws-vault" does not exist. Please add a key first
This is in Ubuntu 17.10
Any pointers? thanks
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 2
- Comments: 19 (2 by maintainers)
Setting
export AWS_VAULT_BACKEND=secret-servicein .bashrc works for me using aws-vault v4.2.1I guess the output of
aws-vault --versionandAWS_VAULT_BACKEND=secret-service aws-vault --debug exec default -- envcould be useful to debug this.I think this should fix it: https://github.com/99designs/aws-vault/pull/226
For me it seems like @crielly is right.
The keyring library used to set collection name to ‘awsvault’. This was removed, and they added support for setting
ServiceNameandLibSecretCollectionNamewhereLibSecretCollectionNameis set toServiceNameif omitted.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.
I just tested this on Fedora 27 with gnome-keyring 3.20.1 and libsecret 0.18.5-5.fc27; it works as @gunnaringe says. Thanks for that patch!
I am afraid I don’t have the skills to provide a patch, all I can do is to provide feedback. And that’s done 😃