From 7eeff41e3257e11c4302f6c65c3be6bb11e5fc68 Mon Sep 17 00:00:00 2001 From: Walter Medvedeo Date: Tue, 4 Jun 2024 14:49:44 +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 255f463cf..1b40c3328 100644 --- a/serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc +++ b/serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc @@ -169,7 +169,7 @@ To configure a common PostgreSQL service instance for all the supporting service 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: -* If a supporting service, has a configured persistence, for example, the field `services.dataIndex.persistence` is configured. That configuration will apply. +* If a supporting service has a configured persistence, for example, the field `services.dataIndex.persistence` is configured. That configuration will apply. * If a supporting service, has no configured persistence, for example, the field `services.dataIndex.persistence` is not set at all, the persistence configuration will be taken from the current platform.