Is your feature request related to a problem? Please describe.
Currently we can build lskv with a public or private kv map. It might be desirable to have a split at runtime for this to have keys under some prefixes be secret. For example, using it as a datastore for configuration management secrets may not want to be visible in the ledger whereas general configs may be ok to have public.
Describe the solution you'd like
Be able to, through config and governance operations, set the prefixes for private keys. Writes and reads to these keys then work on the respective map based on the prefix configuration.
Additional context
Note, this is unrelated to user authentication which is an orthogonal issue.
Is your feature request related to a problem? Please describe.
Currently we can build lskv with a public or private kv map. It might be desirable to have a split at runtime for this to have keys under some prefixes be secret. For example, using it as a datastore for configuration management secrets may not want to be visible in the ledger whereas general configs may be ok to have public.
Describe the solution you'd like
Be able to, through config and governance operations, set the prefixes for private keys. Writes and reads to these keys then work on the respective map based on the prefix configuration.
Additional context
Note, this is unrelated to user authentication which is an orthogonal issue.