How do I read every Vault key.

[Frank James]

Situation: Imagine working with 50x secrets. You have no idea what they are all called. You essentially want to run an ls command (or dir?) to see what there is?

[Armon Dadgar]

Hey Frank,

We a have a ticket open to support listing of secrets, and its on the roadmap, but

there are lots of heavy lifting required to make it happen in core. Hang tight!

Best Regards,

Armon Dadgar

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/vault/issues
IRC: #vault-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Vault" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vault-tool+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/e7e2faf7-71f1-4edb-92a2-bd84d1587c9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jeromy Labit]

Although I don't think you can do it natively in Vault (see Armon's response), there is a way to do it if you are using Consul as a backend since that backend allows you to recursively list keys. You will not be able to see the actual data associated with those keys, because that is encrypted, but the keys (read the secret names: secret/foo, secret/bar) can be collected.

I have not tried with other physical backends, only Consul... so....

[K TT]

I was curious if this ever got resolved.
I realize I can get the information out of consult but it's not clean way to do it and it may not be portable to other backends.

Thank you.

KTT