wmedvede commented on code in PR #713:
URL:
https://github.com/apache/incubator-kie-kogito-docs/pull/713#discussion_r2003447197
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc:
##########
@@ -104,6 +104,27 @@ The ephemeral deployment of a service requires no
additional configurations than
The PostgreSQL persistence of a service is supported by a PostgreSQL server
instance that you must previously install on the cluster.
The administration of that instance is totally independent of the
{operator_name} scope, and to connect a supporting service with it, you must
only configure the correct database connection parameters.
+==== {product_name} Operator Database Migrator capabilities
+The {product_name} Operator offers out of the box database migration features,
which help in configuring the databases for use by Data Index and/or Jobs
Service.
+
+The term database migration refers to either initializing a given Data Index
or Jobs Service database to the schema needed by them or applying data or
schema updates as new versions are released.
+
+{product_name} Operator offers jobs based database migration capabilities
along with two other modes: service based database migration and none.
+
+The {product_name} Operator offered database migration modes are described as
follows.
Review Comment:
```suggestion
```
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc:
##########
@@ -104,6 +104,27 @@ The ephemeral deployment of a service requires no
additional configurations than
The PostgreSQL persistence of a service is supported by a PostgreSQL server
instance that you must previously install on the cluster.
The administration of that instance is totally independent of the
{operator_name} scope, and to connect a supporting service with it, you must
only configure the correct database connection parameters.
+==== {product_name} Operator Database Migrator capabilities
+The {product_name} Operator offers out of the box database migration features,
which help in configuring the databases for use by Data Index and/or Jobs
Service.
+
+The term database migration refers to either initializing a given Data Index
or Jobs Service database to the schema needed by them or applying data or
schema updates as new versions are released.
Review Comment:
```suggestion
The term database migration refers to either initializing a given Data Index
or Jobs Service database to the schema needed by them, or applying data or
schema updates as new versions are released.
```
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc:
##########
@@ -104,6 +104,27 @@ The ephemeral deployment of a service requires no
additional configurations than
The PostgreSQL persistence of a service is supported by a PostgreSQL server
instance that you must previously install on the cluster.
The administration of that instance is totally independent of the
{operator_name} scope, and to connect a supporting service with it, you must
only configure the correct database connection parameters.
+==== {product_name} Operator Database Migrator capabilities
+The {product_name} Operator offers out of the box database migration features,
which help in configuring the databases for use by Data Index and/or Jobs
Service.
+
+The term database migration refers to either initializing a given Data Index
or Jobs Service database to the schema needed by them or applying data or
schema updates as new versions are released.
+
+{product_name} Operator offers jobs based database migration capabilities
along with two other modes: service based database migration and none.
+
+The {product_name} Operator offered database migration modes are described as
follows.
+
+.Jobs based database migration
+In this mode, the {product_name} Operator creates a Kubernetes Job and uses
the database migrator component to migrate configured databases. You would
typically use this mode when running in non-development scenarios such as
Production environments, where there could be an existing database for use by
Data Index and/or Jobs Service.
+
+.Service based database migration
+In this mode, the {product_name} Operator does not create a Kubernetes Job and
hence does not use the database migrator component to migrate configured
databases. In this mode, thus the Data Index or Jobs Service are responsible to
migrate the configured databases. You would typically use this mode when
running in development scenarios such as local environments, where you are
testing scenarios with clean state everytime you deploy and run.
+
+.None mode
Review Comment:
```suggestion
==== None mode
```
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc:
##########
@@ -104,6 +104,27 @@ The ephemeral deployment of a service requires no
additional configurations than
The PostgreSQL persistence of a service is supported by a PostgreSQL server
instance that you must previously install on the cluster.
The administration of that instance is totally independent of the
{operator_name} scope, and to connect a supporting service with it, you must
only configure the correct database connection parameters.
+==== {product_name} Operator Database Migrator capabilities
+The {product_name} Operator offers out of the box database migration features,
which help in configuring the databases for use by Data Index and/or Jobs
Service.
+
+The term database migration refers to either initializing a given Data Index
or Jobs Service database to the schema needed by them or applying data or
schema updates as new versions are released.
+
+{product_name} Operator offers jobs based database migration capabilities
along with two other modes: service based database migration and none.
+
+The {product_name} Operator offered database migration modes are described as
follows.
Review Comment:
I think this line we can remove line since we are immediately describing the
modes.
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc:
##########
@@ -104,6 +104,27 @@ The ephemeral deployment of a service requires no
additional configurations than
The PostgreSQL persistence of a service is supported by a PostgreSQL server
instance that you must previously install on the cluster.
The administration of that instance is totally independent of the
{operator_name} scope, and to connect a supporting service with it, you must
only configure the correct database connection parameters.
+==== {product_name} Operator Database Migrator capabilities
+The {product_name} Operator offers out of the box database migration features,
which help in configuring the databases for use by Data Index and/or Jobs
Service.
+
+The term database migration refers to either initializing a given Data Index
or Jobs Service database to the schema needed by them or applying data or
schema updates as new versions are released.
+
+{product_name} Operator offers jobs based database migration capabilities
along with two other modes: service based database migration and none.
+
+The {product_name} Operator offered database migration modes are described as
follows.
+
+.Jobs based database migration
Review Comment:
```suggestion
==== Jobs based database migration
```
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/supporting-services.adoc:
##########
@@ -104,6 +104,27 @@ The ephemeral deployment of a service requires no
additional configurations than
The PostgreSQL persistence of a service is supported by a PostgreSQL server
instance that you must previously install on the cluster.
The administration of that instance is totally independent of the
{operator_name} scope, and to connect a supporting service with it, you must
only configure the correct database connection parameters.
+==== {product_name} Operator Database Migrator capabilities
+The {product_name} Operator offers out of the box database migration features,
which help in configuring the databases for use by Data Index and/or Jobs
Service.
+
+The term database migration refers to either initializing a given Data Index
or Jobs Service database to the schema needed by them or applying data or
schema updates as new versions are released.
+
+{product_name} Operator offers jobs based database migration capabilities
along with two other modes: service based database migration and none.
+
+The {product_name} Operator offered database migration modes are described as
follows.
+
+.Jobs based database migration
+In this mode, the {product_name} Operator creates a Kubernetes Job and uses
the database migrator component to migrate configured databases. You would
typically use this mode when running in non-development scenarios such as
Production environments, where there could be an existing database for use by
Data Index and/or Jobs Service.
+
+.Service based database migration
Review Comment:
```suggestion
==== Service based database migration
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
