Description
Description
User had an error in the application code that created the wrong keys. They wanted to see all of the keys in the database to debug, but our clients did not have that method.
Justification
Adding support for this command will enable debugging in cases where it is helpful to track the keys added to the database
Implementation Strategy
We should support the Redis keys command with simple globbing to allow an optional substring to be matched. The full Redis regular expression support is not necessary to reimplement for our users; however, an advanced user can stll take advantage of it by putting the special characters into their substring query. We won't try to escape them.
As a follow-on to this work, we can look into key inspection features that could categorize the entry behind a key in more detail as to the type of key (model/script/tensor/metadata/unknown) -- and for tensors and metadata, the datatype of values in the key