Skip to content
Discussion options

You must be logged in to vote

Currently there's no plan, we're trying to limit the scope of the storage operations to avoid turning KM into a file manager or a DB abstraction. Any new feature added on one storage (e.g. Azure Blob) would have to be implemented in all the storage extensions for consistency, which is quite expensive.

That said, the suggestion is to use the SDK of your storage choice, to access the storage and run custom operations. For instance, if you're using KM with Azure Blobs, you can leverage the Azure Storage SDK to browse the storage account, list folders and files.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by dluc
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
1. Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #478 on June 04, 2024 19:37.