Method for checking is KV exists #82
Assignees
Comments
asabya
added a commit
that referenced
this issue
Jan 25, 2022
* addressing #119, uploading same file multiple times * addressing #122, file delete Matadata unmarshal * addressing #123, fix response for non-existing pod * addressing #127, server requires postageBlockId to run * addressing #119, backup old file in case same name * code cleanup * code cleanup * code cleanup * code cleanup * addressing #117 and #118, issues related to pod deletion (#1) * addressing #117 and #118, issues related to pod deletion * fix reploading deleted file * fixes #141, rmdir updates feed with magicword * fixing #139 * fix #140, accept mutable bool in request * #102 handle exception for invalid json * related to #100, doc new podname missing * fix #124, handle removed root directory * handle #96 * handle #24, use shlex to parse prompt args * fixed #19, pod deletion requires password * check for root dir presence in mkdir * mod tidy (#146) * mod tidy * manually restore vendor * manually restore vendor * fix #86, shared pod removed from list * minor changes * #92, table name added in count response * fix w/ deepsource recommendation * fix w/ deepsource recommendation * #102, add test for invalid json * server running from config vales * fix lint errors * fix flag usage * add default variables * rebase * resolve 163 * handle #172 * handle #138, new method for kv/entry/get * #130 handled, /pod/present api added * podPresent only for loggedin user * #82, add /kv/present * #157, add basic string validation * update readme * update openapi (#180) * update openapi * update version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be great if we had a method for checking is key-value exists.
At this moment we could only get all KV and with our KV in this list.
The text was updated successfully, but these errors were encountered: