Yaron Schneider

> I think this is a good thing to add to resiliency in Dapr. I think we just need to be very clear that it'll be on a per-sidecar basis...

cc @halspang

@piotrkpc FYI we are in release code freeze for 1.8 at 6/21.

@halspang can you review this also please? overall looks good.

@1046102779 does this solve the issue? https://docs.dapr.io/operations/security/api-token/

> Is it possible to ask if this can be added to the [v1.7 milestone](https://github.com/dapr/dapr/milestone/13)? Or is it too large of a feature request? It's probably too large for 1.7.....

That's an interesting proposal! In the end, users still need to build their own `daprd` binary, then build a container image and store it in a registry, correct? I'm interested...

> We need to change the approach: > > * Stops new incoming messages right away for PubSub, Binding and Service Invocation. > * Continue allowing outgoing API calls during...

Thanks for raising this @clemensv. Dead letter topics are off by default, and are an opt-in feature. I suggest we move this to docs as this is really about documenting...

Reading [this](https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dead-letter-queues) link, it seems that if Dapr DLQ isn't enabled, AND if any of the scenarios leading to a message going into the ASB DLQ occurs, then from Dapr's...