CredHub CLI "find -n ''" should find all credentials, not none about credhub HOT 3 CLOSED

Hey Amit -

Is there a use case you have in mind for listing every credential that exists in the system? My instinct is to not add this until there is a need and we feel that this is a good way to accomplish it.

My guess is that a user would be looking for something vaguely specific - a partial name, deployment name or path - not just listing all of the things that exist. I will certainly validate this as feedback rolls in.

from credhub.

My use case was hygiene. I discovered that some random test credential had been left around during development/testing, and I wanted to make sure there weren't any other credentials lying around. I can imagine people may want to be able to audit what's living around in their CredHub for various reasons.

It's also just inconsistent behaviour. ./credhub find -n <X> should match all credentials containing the substring <X>. It's awkward UX that the empty string behaves differently, it was definitely surprising/unexpected behaviour. It's contrary to how grep and other CLI tools people are familiar with work.

from credhub.

This issue was moved to cloudfoundry/credhub-cli#8

from credhub.