From fc1a8d129562355ca382e645a71f75a3fc52c881 Mon Sep 17 00:00:00 2001 From: Walter Medvedeo Date: Tue, 4 Jun 2024 14:47:12 +0200 Subject: [PATCH] Update serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc Co-authored-by: nmirasch --- .../modules/ROOT/pages/cloud/operator/supporting-services.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc b/serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc index e9e142daa..255f463cf 100644 --- a/serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc +++ b/serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc @@ -165,7 +165,7 @@ kubectl create secret generic postgres-secrets-example --from-literal=POSTGRESQ [#common-persistence-configuration] === Common PostgreSQL persistence configuration -To configure common a PostgreSQL service instance for all the supporting services you must read, xref:cloud/operator/using-persistence.adoc#configuring-persistence-using-the-sonataflowplatform-cr[Configuring the persistence using the SonataFlowPlatform CR]. +To configure a common PostgreSQL service instance for all the supporting services you must read, xref:cloud/operator/using-persistence.adoc#configuring-persistence-using-the-sonataflowplatform-cr[Configuring the persistence using the SonataFlowPlatform CR]. In that case, the {operator_name} will automatically connect any of the supporting services with that common server configured in the field `spec.persistence`. And, similarly to the workflow's persistence, the following precedence rules apply: