Update automation pipeline docs with new changes.

abeykoon · abeykoon · commit 2a8a38613dd8 · 2025-11-17T20:21:08.000+05:30
diff --git a/en/pe-docs/docs/devops/automation-pipelines/inbuilt-templates.md b/en/pe-docs/docs/devops/automation-pipelines/inbuilt-templates.md
@@ -1,17 +1,17 @@
 When configuring a pipeline, you can use built-in pipeline templates provided by Choreo. These templates include pre-defined functionality that can simplify and accelerate pipeline creation.
 
-[Choreo’s pipeline specification](./specification.md) supports referencing these templates using the following syntax:
+[Choreo’s pipeline specification](https://github.com/wso2/choreo-pipeline-specification/tree/main/docs/specification) supports referencing these templates using the following syntax:
 
-```
+```yaml
 steps:
-  - name: Build
+  - name: <step name>
     template: choreo/<template name>
 ```
 
 ## Available Built-in Templates
 
 !!! info "Note"
-    The list of built-in templates is continuously growing.
+    The list of built-in templates is continuously growing. Check [complete list of Choreo built-in templates](https://github.com/wso2/choreo-pipeline-specification/blob/main/docs/specification/built-in-templates.md)
 
 ??? "choreo/buildpack-build@v1"
     Builds applications using supported buildpacks within Choreo. This is used by Choreo’s default build pipeline.
@@ -42,3 +42,41 @@ steps:
 
 ??? "choreo/prism-build@v1"
     Builds Prism projects.
+
+## Publish to Choreo Marketplace
+
+At the end of all the resource provisioning steps in the automation pipeline, to publish metadata and credentials of provisioned resources to the Choreo marketplace, use inbuilt pipeline template `choreo/marketplace-publish@v1`. This template accepts an input argument called `resource` which needs to have a specific structure. Following is an example used to publish details of a provisioned MSSQL database.
+
+{% raw %}
+```yaml
+steps:
+  - name: publish-marketplace
+    template: choreo/marketplace-publish@v1
+    arguments:
+      parameters:
+        - name: resource
+          yamlObject:
+            name: "mssql-db-$ENVIRONMENT"
+            version: 1.0.0
+            category: Database
+            description: MSSQL Database
+            tags:
+              - dev
+            properties:
+              databaseName: "{{steps.run-terraform.outputs.parameters.sql_database_name}}"
+              sqlServerFQDN: "{{steps.run-terraform.outputs.parameters.sql_server_fqdn}}"
+            connectionCredentials:
+              - environments:
+                  - Development
+                parameters:
+                  - key: ConnectionString
+                    value: "{{steps.run-terraform.outputs.parameters.connection_string}}"
+                    isSecret: false
+                  - key: DBUsername
+                    value: "{{steps.run-terraform.outputs.parameters.db_user_username}}"
+                    isSecret: true
+                  - key: DBUserPassword
+                    value: "{{steps.run-terraform.outputs.parameters.db_user_password}}"
+                    isSecret: true
+```
+{% endraw %}
diff --git a/en/pe-docs/docs/devops/automation-pipelines/introduction.md b/en/pe-docs/docs/devops/automation-pipelines/introduction.md
@@ -1,8 +1,6 @@
 # What are Automation Pipelines
 
 !!! info "Note"
-    Automation pipeline capabilities are only available in paid plans for private data plane organizations.
+    Automation pipeline capabilities are only available for private data plane organizations.
 
-Choreo provides the capability to define and run any automated workflow within your IDP infrastructure. You can write your automation pipeline using the [Choreo pipeline syntax](./specification.md) which is a simplified version of [Argo workflows syntax](https://argoproj.github.io/workflows/) syntax.
-
-There are a few variations of automation pipelines - CI pipelines, CD pipelines and Infrastructure provisioning pipelines depending on what you are automating.
+Choreo provides the capability to define and run any automated workflow with multiple steps within your IDP infrastructure. You can write your automation pipeline using the [Choreo pipeline syntax](https://github.com/wso2/choreo-pipeline-specification/tree/main/docs/specification) which is a simplified version of [Argo workflows syntax](https://argoproj.github.io/workflows/) syntax.
diff --git a/en/pe-docs/docs/devops/automation-pipelines/manage-automation-pipeline.md b/en/pe-docs/docs/devops/automation-pipelines/manage-automation-pipeline.md
@@ -3,11 +3,12 @@
 Choreo allows to define automation pipelines at organization level. Follow these steps to create an automation pipeline.
 
 1. Sign in to the [Choreo Console](https://console.choreo.dev/).
-2. In the left navigation menu, click **DevOps** and then click **Automation Pipelines**.
-3. Click **+ Create**.
-4. You can define an inline yaml or import from GitHub
+2. Open **Platform Operations** perspective.
+3. In the left navigation menu, click **DevOps** and then click **Automation Pipelines**.
+4. Click **+ Create**.
+5. You can define an inline yaml or import from GitHub
 
-## Define pipeline within Choreo
+## Define Pipeline within Choreo
 
 This option is useful when you are testing a pipeline or if you like to let Choreo to keep your pipeline definitions.
 
@@ -18,12 +19,12 @@ This option is useful when you are testing a pipeline or if you like to let Chor
 
 This pipeline definition is managed within Choreo. You can update it after defining as well.
 
-## Import pipeline from Git
+## Import Pipeline from Git
 
-If your organization manages pipelines in Git, you can authorize and let Choreo to refer it. It could be a monolithic repository having multiple pipelines.
+If your organization manages pipelines in Git (GitHub, Bitbucket or GitLab), you can authorize and let Choreo to refer it. It could be a monolithic repository having multiple pipelines.
 
 1. Under `Import Pipeline from Git` Click on the Git provider to authorize, and proceed with steps to grant access.
-2. You can select **Repository**, **Branch** and Specific **Pipeline Yaml** File within and directory in the repository.
+2. You can select **Repository**, **Branch** and Specific **Pipeline Yaml** file within a directory in the repository.
 3. Provide a name by which you can identify the pipeline.
 4. Optionally provide a description
 5. Click **Create**
@@ -33,7 +34,7 @@ Created pipelines will be listed in a tabular view.
 
 # Edit Automation Pipelines
 
-Editing is only possible for pipelines defined within Choreo. Click **Edit Pipeline YAML** and in the right side panel that opens up you can edit the pipeline definition. You can view the pipeline definition in full screen view as well by maximizing the panel.
+Editing is only possible for pipelines defined within Choreo. Click **Edit Pipeline YAML** and in the right side panel that opens up you can edit the pipeline definition. You can view the pipeline definition in full-screen view as well by maximizing the panel.
 
 !!! info "Note"
     Once a pipeline is edited, you cannot roll back to a previous version.
@@ -44,4 +45,3 @@ To update the pipeline, modify it in Git and trigger a new run.
 # Delete Automation Pipelines
 
 In the pipeline listing, under the **Actions** column, click the **Delete** icon. A confirmation pop-up will appear. Upon confirmation, the pipeline and all its associated runs will be permanently removed from Choreo.
-
diff --git a/en/pe-docs/docs/devops/automation-pipelines/run-automation-pipeline.md b/en/pe-docs/docs/devops/automation-pipelines/run-automation-pipeline.md
@@ -2,7 +2,7 @@ After a pipeline is defined, you can execute it. The pipeline may need some inpu
 
 # Add Pipeline Variables and Secrets
 
-The pipelines are defined at the organization level. Thus the variables defined for them are injected at the same level. Learn more on how to define a input variable in your pipeline at [Variables and Secrets - Choreo Pipelines Specification](abc). Follow these steps to define inputs and their values for a given pipeline.
+The pipelines are defined at the organization level. Thus the variables defined for them are injected at the same level. Learn more on how to define a input variable in your pipeline at [Variables and Secrets - Choreo Pipelines Specification](https://github.com/wso2/choreo-pipeline-specification/blob/36f292dcb34bdcf2292f5c8537efc57ef5f5e5a4/docs/specification/environment-variables.md). Follow these steps to define inputs and their values for a given pipeline.
 
 1. Click on **Pipeline Variables & Secrets** at upper right corner of the pipeline page.
 2. A panel will appear on the right side. To add a variable, under **Variables** section, add a new one by providing the Name and Value. The variable name must exactly match the name expected by the pipeline.
@@ -11,11 +11,25 @@ The pipelines are defined at the organization level. Thus the variables defined
 !!! info "Note"
     Once a secret is added, it is securely uploaded to the environment’s configured vault and injected into the pods running the workflow. You will not be able to view the secret value again after it is added.
 
-## Manage existing Pipeline Variables and Secrets
+## Manage Existing Pipeline Variables and Secrets
 
 To update or remove a secret, click the three vertical dots in the upper-right corner of the variable box in the Choreo UI. From the menu, choose the appropriate action.
 
-# Run pipeline
+## Pipeline Parameters
+
+Parameters are another type of variables referred by automation pipelines. Speciality of these variables is, before running the pipeline, user needs to choose a value for the parameters out of specified.
+
+In pipeline definition, specify parameters like below.
+
+```
+parameters:
+  - name: environment
+    default: "Development"
+    enum: ["Development", "Production"]
+    displayName: "Environment"
+```
+
+# Run Pipeline
 
 Once the pipeline inputs are configured, click **Start New Run** to trigger a workflow run. The run will use the latest version of the pipeline definition along with the configured inputs.
 
@@ -27,16 +41,16 @@ Under the Runs table, a new row will appear displaying a unique **Run ID** for t
     - **Failed**: One or more steps in the pipeline failed.
     - **Stopped**: The pipeline was manually stopped.
 3. **Start Time** – The timestamp when the pipeline run was triggered.
-4. **Duration** – The total time taken to execute the pipeline. If the pipeline runs for more than a predefined threshold (e.g., xx minutes), it will be automatically force-stopped by Choreo.
+4. **Duration** – The total time taken to execute the pipeline. If the pipeline runs for more than a predefined threshold (default 60 minutes), it will be automatically force-stopped by Choreo.
 
 
-# View pipeline logs
+## View Pipeline Logs
 
 Click **View Logs** for a selected pipeline run in the Runs table. This opens a panel on the right, displaying logs for each step of the pipeline. You can close or maximize the log panel using the icons in the upper-right corner of the panel.
 
 !!! info "Note"
-    Choreo keeps pipeline logs maximum for 30 days. 
+    Choreo keeps pipeline logs maximum for 30 days.
 
-# Stop a pipeline run
+## Stop a Pipeline Run
 
 One a pipeline run is triggered, Click on **View Logs** and then in the log panel that opens to the right, click on **Stop Run**.
diff --git a/en/pe-docs/docs/devops/automation-pipelines/specification.md b/en/pe-docs/docs/devops/automation-pipelines/specification.md
