Closed thomastaylor312 closed 2 months ago
Ok, I think I have addressed most comments. @kate-goldenring @dicej would love to make sure you're still good with everything as well
Heads up that I made one more commit with the changes discussed in https://github.com/WebAssembly/wasi-keyvalue/pull/41#discussion_r1548559842
Ok, I have pushed an update for the list-keys
to use a cursor. Please let me know how it looks
Ok, looks like we have a good consensus! Going to go ahead and merge. If there were any other missing docs or issues, let me know and I'll open a follow up
This is a wide ranging PR focused on trimming down and streamlining the keyvalue interface. This was a collaborative effort between Spin maintainers (@kate-goldenring and @dicej), wasmCloud maintainers (@thomastaylor312), @lukewagner, @Mossaka, and many others. Some of the key changes include:
bucket
to construct them rather than passing the bucket parameter each timestore
interface. Please note that this doesn't mean we won't support more consistency levels in the future, just that what is enumerated instore
is the most common expectations based on what our projects users were doing as well as comparing other similar offerings across the spaceAfter noodling on it some more with involved parties, we decided to keep the watch interface in here as well, whereas we were initially thinking we could just use
wasi:messaging
instead.