kaldesai commented on code in PR #634:
URL:
https://github.com/apache/incubator-kie-kogito-docs/pull/634#discussion_r1609244345
##########
serverlessworkflow/modules/ROOT/pages/job-services/core-concepts.adoc:
##########
@@ -32,18 +23,31 @@ For example, every time the workflow execution reaches a
state with a configured
image::job-services/Time-Based-States-And-Job-Service-Interaction.png[]
To set up this integration you can use different
xref:use-cases/advanced-developer-use-cases/job-service/quarkus-extensions.adoc#job-service-quarkus-extensions[communication
alternatives], that must be configured by combining the Job Service and the
Quarkus Workflow Project configurations.
+Alternatively, when you work with {operator_name} workflow deployments, the
operator can manage all these configurations.
[NOTE]
====
If the project is not configured to use the Job Service, all time-based
actions will use an in-memory implementation of that service.
However, this setup must not be used in production, since every time the
application is restarted, all the timers are lost, making it unsuitable for
serverless architectures where applications might scale to zero at any time,
etc.
====
+[IMPORTANT]
+====
+If you are working with the {operator_name} be sure that you read this section
<<_sonataflow_operator_managed_deployment, {operator_name} managed
deployments>>.
+====
+
== Jobs life-span
Since the main goal of the Job Service is to work with the active jobs, such
as the scheduled jobs that needs to be executed, when a job reaches a final
state, it is removed from the Job Service.
However, in some cases where you want to keep the information about the jobs
in a permanent repository, you can configure the Job Service to produce status
change events, that can be collected by the {data_index_xref}[Data Index
Service], where they can be indexed and made available by GraphQL queries.
+== {operator_name} managed deployment
+
+When you work with the {operator_name} to deploy your workflows, there's no
need to do any manual Job Service installation nor configuration, the operator
has already the ability to do that.
Review Comment:
```suggestion
When you work with the {operator_name} to deploy your workflows, there's no
need to do any manual Job Service installation or configuration, the operator
already has the ability to do that.
```
--
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]
