772, constant retry examples using incorrect maxInterval option (#779)

Signed-off-by: LordMsz <[email protected]> Co-authored-by: Artur Souza <[email protected]>
dapr · Feb 3, 2023 · 5ac2a30 · 5ac2a30
1 parent 26d2318
commit 5ac2a30
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/resiliency/service-to-component-resiliency.md b/resiliency/service-to-component-resiliency.md
@@ -84,7 +84,7 @@ Policies defined in the resiliency.yaml spec:
 ```yaml
 retryForever:
   policy: constant
-  maxInterval: 5s
+  duration: 5s
   maxRetries: -1 
 
 circuitBreakers:

diff --git a/resiliency/service-to-service-resiliency.md b/resiliency/service-to-service-resiliency.md
@@ -133,7 +133,7 @@ Policies defined in the resiliency.yaml spec:
 ```yaml
 retryForever:
   policy: constant
-  maxInterval: 5s
+  duration: 5s
   maxRetries: -1 
 
 circuitBreakers:

diff --git a/service_invocation/resources/resiliency.yaml b/service_invocation/resources/resiliency.yaml
@@ -10,7 +10,7 @@ spec:
     retries:
       retryForever:
         policy: constant
-        maxInterval: 5s
+        duration: 5s
         maxRetries: -1 
 
     circuitBreakers:

diff --git a/state_management/resources/resiliency.yaml b/state_management/resources/resiliency.yaml
@@ -10,7 +10,7 @@ spec:
     retries:
       retryForever:
         policy: constant
-        maxInterval: 5s
+        duration: 5s
         maxRetries: -1 
 
     circuitBreakers: