From a40364799fc8050dcc887e94a696fd1d42817e4f Mon Sep 17 00:00:00 2001 From: halspang <70976921+halspang@users.noreply.github.com> Date: Mon, 10 Oct 2022 14:38:22 -0700 Subject: [PATCH] Update daprdocs/content/en/operations/resiliency/policies.md Co-authored-by: greenie-msft <56556602+greenie-msft@users.noreply.github.com> Signed-off-by: halspang <70976921+halspang@users.noreply.github.com> --- daprdocs/content/en/operations/resiliency/policies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/operations/resiliency/policies.md b/daprdocs/content/en/operations/resiliency/policies.md index 8e4d9d005..e75ca1f99 100644 --- a/daprdocs/content/en/operations/resiliency/policies.md +++ b/daprdocs/content/en/operations/resiliency/policies.md @@ -160,7 +160,7 @@ If these policies are defined, they would be used for every operation to a servi | ConfigurationComponentOutbound | All configuration component operations. | DefaultConfigurationComponentOutboundPolicy | | LockComponentOutbound | All lock component operations. | DefaultLockComponentOutboundPolicy | -For all generic policies, they will only be used if the operation being executed matches the policy and if there is no more specific policy targeting it. +Default policies are applied if the operation being executed matches the policy type and if there is no more specific policy targeting it. For example, we have a system with 3 applications, AppA, AppB, and AppC. The following resiliency configuration is applied to the cluster: