[SRVLOGIC-404] Add info about Dev, Preview, GitOps deployment profiles

first batch of mode to profile corr

second batch of mode to profile corr

fix double signs

improvements for the overview section

remove profile from list

improve heading

remove parentheses GitOps

qe feedback

qe feedback no2

qe feedback no2 fix

pr feedback

Author: ochromy

modules/serverless-logic-deploying-workflows-dev-mode.adoc

@@ -4,9 +4,9 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="serverless-logic-deploying-workflows-dev-mode_{context}"]
-= Deploying workflows in Dev mode
+= Deploying workflows using the Dev profile
 
-You can deploy your local workflow on {ocp-product-title} in Dev mode. You can use this deployment to experiment and modify your workflow directly on the cluster, seeing changes almost immediately. Dev mode is designed for development and testing purposes. It is ideal for initial development stages and for testing new changes.
+You can deploy your local workflow on {ocp-product-title} using the Dev profile. You can use this deployment to experiment and modify your workflow directly on the cluster, seeing changes almost immediately. Dev profile is designed for development and testing purposes. Because it automatically reloads the workflow without restarting the container, it is ideal for initial development stages and for testing workflow changes in a live environment.
 
 .Prerequisites
 
@@ -66,8 +66,8 @@ spec:
         end: true
 ----
 +
-<1> is a workflow_name
-<2> indicates that you must deploy the workflow in Dev mode
+<1> Is a <workflow_name>.
+<2> Indicates that you must deploy the workflow using the Dev profile.
 
 . To deploy the application, apply the YAML file by entering the following command:
 +

serverless-logic/serverless-logic-getting-started/serverless-logic-deploying-workflows.adoc

@@ -1,32 +1,38 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="serverless-logic-deploying-workflows"]
-= Deploying workflows
+= Deployment options and deploying workflows
 include::_attributes/common-attributes.adoc[]
 :context: serverless-logic-deploying-workflows
 
 toc::[]
 
-You can deploy the {ServerlessLogicProductShortName} workflows on the cluster in two modes: Dev mode and Preview mode.
+You can deploy the {ServerlessLogicProductShortName} workflows on the cluster using one of three deployment profiles: 
+
+* Dev
+* Preview
+* GitOps
+
+Each profile defines how the Operator builds and manages workflow deployments, including image lifecycle, live updates, and reconciliation behavior.
 
 include::modules/serverless-logic-deploying-workflows-dev-mode.adoc[leveloffset=+1]
 
 [id="serverless-logic-deploying-workflows-preview-mode_{context}"]
-== Deploying workflows in Preview mode
+== Deploying workflows using the Preview profile
 
-You can deploy your local workflow on {ocp-product-title} in Preview mode. This allows you to experiment and modify your workflow directly on the cluster, seeing changes almost immediately. Preview mode is used for final testing and validation before deploying to production. It also ensures that workflows will run smoothly in a production-like setting.
+You can deploy your local workflow on {ocp-product-title} using the Preview profile. This allows you to validate and test workflows in a production-like environment directly on the cluster. Preview profile is ideal for final testing and validation before moving workflows to production, as well as for quick iteration without directly managing the build pipeline. It also ensures that workflows will run smoothly in a production-like setting.
 
 .Prerequisites
 
 * You have an {ServerlessLogicOperatorName} installed on your cluster.
 * You have access to an {ServerlessLogicProductName} project with the appropriate roles and permissions to create applications and other workloads in {ocp-product-title}.
 * You have installed the OpenShift CLI `(oc)`.
 
-To deploy a workflow in Preview mode, {ServerlessLogicOperatorName} uses the build system on {ocp-product-title}, which automatically creates the image for deploying your workflow.
+To deploy a workflow in Preview profile, {ServerlessLogicOperatorName} uses the build system on {ocp-product-title}, which automatically creates the image for deploying your workflow.
 
 The following sections explain how to build and deploy your workflow on a cluster using the {ServerlessLogicOperatorName} with a `SonataFlow` custom resource.
 
 [id="serverless-logic-configuring-workflows-preview-mode_{context}"]
-=== Configuring workflows in Preview mode
+=== Configuring workflows in Preview profile
 
 include::modules/serverless-logic-workflow-base-builder-image.adoc[leveloffset=+3]
 include::modules/serverless-logic-workflow-base-builder-dockerfile.adoc[leveloffset=+3]
@@ -38,6 +44,53 @@ include::modules/serverless-logic-building-deploying-workflow-preview-mode.adoc[
 include::modules/serverless-logic-verifying-workflow-deployment-preview-mode.adoc[leveloffset=+2]
 include::modules/serverless-logic-restarting-the-build-preview-mode.adoc[leveloffset=+2]
 
+[id="serverless-logic-deploying-workflows-gitops-mode_{context}"]
+== Deploying workflows using the GitOps profile
+
+[IMPORTANT]
+====
+Use the GitOps profile only for production deployments.  
+For development, rapid iteration, or testing, use the Dev or Preview profiles instead.
+====
+
+You can deploy your local workflow on {ocp-product-title} using the GitOps profile. The GitOps profile provides full control over the workflow container image by allowing you to build and manage the image externally, typically through a CI/CD pipeline such as ArgoCD or Tekton. When a container image is defined in the `SonataFlow` custom resource (CR), the Operator automatically assumes the GitOps profile is being used and it does not attempt to build or modify the image in any way.
+
+.Prerequisites
+
+* You have {ServerlessLogicOperatorName} installed on your cluster.
+* You have access to a {ServerlessLogicProductName} project with the appropriate roles and permissions to create applications and other workloads in {ocp-product-title}.
+* You have installed the OpenShift CLI `(oc)`.
+
+.Procedure
+
+. Specify your container image in your SonataFlow CR:
++
+.Example SonataFlow CR with set GitOps profile
+[source,yaml]
+----
+apiVersion: sonataflow.org/v1alpha08
+kind: SonataFlow
+metadata:
+  annotations:
+    sonataflow.org/profile: gitops
+  name: workflow_name
+spec:
+  flow: <1>
+#...
+  podTemplate:
+    container:
+      image: your-registry/workflow_name:tag
+#...
+----
+<1> The `flow` definition must match the workflow definition used during the build process. When you deploy your workflow using the GitOps profile, the Operator compares this definition with the workflow files embedded in the container image. If the definition and files do not match, the deployment fails.
+
+. Apply your CR to deploy the workflow:
++
+[source,terminal]
+----
+$ oc apply -f <filename>
+----
+
 include::modules/serverless-logic-editing-workflows.adoc[leveloffset=+1]
 include::modules/serverless-logic-testing-workflows.adoc[leveloffset=+1]
 include::modules/serverless-logic-troubleshooting-workflows.adoc[leveloffset=+1]