Open MadsRC opened 9 years ago
Right now VaultDiscover only supports a single generic backend because there is currently no way that I know of to tie a backend's ID on the filesystem to the name of the backend. If you change the following code in vault_discover.py
:
...
for key, value in dir.items():
for k, v in value.items():
return v
...
to
...
return dir
...
You can get back the contents of all generic backends.
If you do this, you'll get something back that looks like this:
{
"logical": {
"8f706d84-61e3-1ce1-6ce1-ae45e1b059ce": {
"servers": {
"_myhost": null,
"_myotherhost": null
}
},
"2f826d64-61e1-1cf1-6ce1-be45e1b087ca": {
"servers": {
"_somehost": null
},
"development": {
"_stuff": null
}
}
}
}
Hi ShadowApex Great Frontend love it. One problem I can link my vaultkee to vault put in my server ip address and for the list url I put in my serverip address again with /v1/ and I get back secret/rrors
Server IP http://9.12.12.1:8200 Listing URL http://9.12.12.1:8200/v1/ Token : ** Backend storage to a file vaultkeediscover : using settings.conf logical_path = /usr/local/bin/storage/logical vault_url = http://localhost:8200
Just can't see any secrets from vault 0.5.0
Hope you can help .. T
Thanks
Hi @chrismichaelmurphy @ShadowApex ,
Did you find any solution for this? I get the same error.
Thanks.
In my test setup I have 2 generic backends for 2 different divisions.
The
explore(rootdir)
function invault_discover.py
does not return the content of both backends. In my test, it only returned the content of one backend.