From 67e9c1baad9a054dbb6ef19e59da2b1b64057651 Mon Sep 17 00:00:00 2001 From: Walter Medvedeo Date: Wed, 22 May 2024 13:12:39 +0200 Subject: [PATCH] Update serverlessworkflow/modules/ROOT/pages/cloud/operator/using-persistence.adoc Co-authored-by: Ricardo Zanini <1538000+ricardozanini@users.noreply.github.com> --- .../modules/ROOT/pages/cloud/operator/using-persistence.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/serverlessworkflow/modules/ROOT/pages/cloud/operator/using-persistence.adoc b/serverlessworkflow/modules/ROOT/pages/cloud/operator/using-persistence.adoc index 93a331ff4..af2c8a814 100644 --- a/serverlessworkflow/modules/ROOT/pages/cloud/operator/using-persistence.adoc +++ b/serverlessworkflow/modules/ROOT/pages/cloud/operator/using-persistence.adoc @@ -160,7 +160,7 @@ And, if the current namespace has an already configured <<_configuring_the_persi * If the SonataFlow CR has a configured persistence, that configuration will apply. * If the SonataFlow CR has no configured persistence, i.e., the field `spec.persistence` is not present at all, the persistence configuration will be taken from the current platform. -* If you don't want the current workflow to use persistence, you must use the following configuration in the SonataFlow CR: `spec.persistence : {}` to ban the SonataFlowPlatform persistence. +* If you don't want the current workflow to use `persistence`, you must use the following configuration in the SonataFlow CR: `spec.persistence : {}` to ignore the `SonataFlowPlatform` persistence configuration. == Persistence configuration and SonataFlow profiles