Josh van Leeuwen

@yaron2 Done

Moving to milestone v1.14 as not enough time for v1.13

Hi @elabedo, does `--dapr-block-shutdown-duration` do what you want? This will block until the app reports as unhealthy which you can control. https://docs.dapr.io/reference/arguments-annotations-overview/

@elabedo the given duration is an upper bound. Dapr will also stop blocking when the app reports as unhealthy, which your application has runtime context for when to do, i.e....

@elabedo it is implied via the statement “from starting until the given duration has elapsed or the application becomes unhealthy” https://docs.dapr.io/reference/arguments-annotations-overview/ I must admit that I remember the verbiage being...

@philliphoff please can you re-enable the socket integration test for windows in this PR? :) they are also quite limited so consider extending them a bit if you want https://github.com/dapr/dapr/blob/53ceb4aa59a57a25de9d76b61b298584f5339354/tests/integration/suite/daprd/pluggable/basic.go#L48

Hi @yejialiango, thanks for the issue! You are correct that in order for (all) Dapr services to pick up changes to Configurations, a restart is required. Today, this process is...

The project should always strive to do things the right way, especially so for security. I don't think we should follow the deprecation policy in this instance as this is...

@ItalyPaleAle it is enabled by default in Kubernetes.

+1 to VenafiCertificate