Yaron Schneider

@JoshVanL can now backport to 1.14

@evhen14 see the failing static checks

So far there hasn't been a need for a v2.0 of an API, but there's no reason why the current versioning scheme couldn't support it if needed. For example in...

Thanks for this detailed proposal, distributed locks for leader elections and similar scenarios is a feature that I've personally wanted to see in Dapr for a long time now. I...

Not closing @seeflood, this is a good proposal and I would like to have this in 1.5 if possible.

@seeflood personally I really favor adding capabilities to existing state stores. There's two reasons for this: 1. Avoiding duplication of code - see the configuration stores, for example. we are...

Thanks @seeflood I think this is a very good iteration of the proposal. Also, since Dapr components are feature oriented, I think it's OK to have a state store with...

> @yaron2 OK. I will start coding recently Hold on for just a bit! I want an approval on this from @artursouza too, then you can start :)

> I have a concern about making the distributed lock API to fit into the state store. These are difference use cases. There might be a way to implement the...

> One more point is how this will affect existing state stores that are stable. Does it mean we have to mark each capability as alpha-beta-stable? I would rather not...