url:"/promotion-policy"

-title:Promotion Workflows

url:"/promotion-workflow"

-title:Product Settings

url:"/product-promotion-props"

-title:YAML specs

url:"/yaml"

sub-pages:

toc:true

*[Promotion Flows]({{site.baseurl}}/docs/promotions/configuration/promotion-flow/) (only account admins)

*[Promotion Policies]({{site.baseurl}}/docs/promotions/configuration/promotion-policy/) (only account admins)

*[Promotion Workflows]({{site.baseurl}}/docs/promotions/configuration/promotion-workflow/)

Enhance your promotion strategies with these advanced configuration options:

* Multi-environment promotion with[Promotion Flows]({{site.baseurl}}/docs/promotions/configuration/promotion-flow/) (only account admins)

* Conditional promotions with[Promotion Policies]({{site.baseurl}}/docs/promotions/configuration/promotion-policy/) (only account admins)

* Automatic validations and gates with[Promotion Workflows]({{site.baseurl}}/docs/promotions/configuration/promotion-workflow/)

* Versioning, properties for promotion, flows and triggers, with[Product Settings]({{site.baseurl}}/docs/promotions/configuration/product-promotion-props/)

If you are more comfortable with YAML, see our[YAML specification examples]({{site.baseurl}}/docs/promotions/configuration/yaml/) for the same.

title:"Configure product promotion settings & flows"

description:"Configure key settings for the product to optimize promotion"

group:promotions

toc:true

Before or after configuring specialized promotion entities such as Promotion Flows, Policies, and Workflows, note that there are product-specific settings crucial to effective, reliable promotions, regardless of the method you use or intend to use.

If you've created products, make sure you have configured the following settings for a consistent promotion experience.

The product version specifies the source of the version you want to promote. By defining the source for retrieving the version, you gain control over what is promoted at each stage.

**Why is it important?**

Setting a source for the version ensures that each promotion action consistently targets the correct version of your product's applications.

This minimizes potential issues due to version discrepancies, maintains application integrity, and provides a traceable version history.

Product properties allow you to specify the files and precise attributes—such as tags, version numbers, or other application attributes—that should be promoted across environments.

**Why is it important?**

Configuring these properties combines precision with automation, enabling promotions that consistently meet your defined requirements.

Defining properties to be promoted for products ensures accuracy and enforces deployment standards that simplify cross-environment promotions.

{% include

image.html

lightbox="true"

file="/images/gitops-promotions/product/product-promotion-settings.png"

url="/images/gitops-promotions/product/product-promotion-settings.png"

alt="Product Settings: Version and properties"

caption="Product Settings: Version and properties"

max-width="60%"

%}

For details, see[Configuring app version and promotable properties]({{site.baseurl}}/docs/products/promotion-version-properties).

If you’ve already created Promotion Flows, you can assign them to products and set up the triggers that initiate these flows based on specific conditions.

Assigning Promotion Flows to a product and configuring their triggers optimizes the automation of your promotion process, reducing manual input and increasing response efficiency. Triggered promotions allow you to promote changes in alignment with pre-defined pipeline conditions, such as matching commit messages or specific code changes. This alignment minimizes human error, ensures promotions happen at the correct time, and maintains a structured, policy-driven workflow.

{% include

image.html

lightbox="true"

file="/images/gitops-promotions/product/product-promotion-flow-triggers.png"

url="/images/gitops-promotions/product/product-promotion-flow-triggers.png"

alt="Product Settings: Promotion Flows & triggers"

caption="Product Settings: Promotion Flows & triggers"

max-width="50%"

%}

For details, see[Configuring promotion flows and triggers]({{site.baseurl}}/docs/products/promotion-flow-triggers/).

[Configure Product Settings]({{site.baseurl}}/docs/products/configure-product-settings/)

[Create products]({{site.baseurl}}/docs/products/create-product/)

max-width="60%"

%}

{:start="8"}

{:start="9"}

1. To commit changes, click**Save Promotion Flow**.

The Promotion Flow is added to the list of Promotion Flows.

In the example, we have already added the`staging` environment.

Now we'll update the dependency on the`production` environment, by selecting`staging`, in addition to`qa`:

{% include

max-width="60%"

%}

Here's the`three-env-promotion` Promotion Flow with the updated dependency.

{% include

max-width="60%"

%}

Here's the YAML view of the same flow with the updated dependency.

{% include

image.html

lightbox="true"

file="/images/gitops-promotions/tutorials/promo-flow-dependency-yaml-view.png"

url="/images/gitops-promotions/tutorials/promo-flow-dependency-yaml-view.png"

alt="YAML view of Promotion Flow with updated dependencies"

caption="YAML view of Promotion Flow with updated dependencies"

max-width="60%"

%}

[Promotion tutorials]({{site.baseurl}}/docs/promotions/promotion-scenarios/)

max-width="60%"

%}

Here's thepromotion flow with the parallel environments:

Here's thePromotion Flow with the parallel environments:

{% include

image.html

max-width="60%"

%}

Here's the YAML view of the Promotion Flow with the parallel environments.

{% include

image.html

lightbox="true"

file="/images/gitops-promotions/tutorials/promo-flow-parallel-yaml-view.png"

url="/images/gitops-promotions/tutorials/promo-flow-parallel-yaml-view.png"

alt="YAML view of Promotion Flow with parallel environments"

caption="YAML view of Promotion Flow with parallel environments"

max-width="60%"

%}

We'll save this as`parallel-env-promotion`.

lightbox="true"

file="/images/gitops-promotions/tutorials/seq-flow-populated-policy.png"

url="/images/gitops-promotions/tutorials/seq-flow-populated-policy.png"

alt="Targetenvironment with policy settings"

caption="Targetenvironment with policy settings"

alt="Targetenvironments with policy settings"

caption="Targetenvironments with policy settings"

max-width="60%"

%}

Here's the YAML view of the promotion flow with the workflows and promotion actions.

{% include

image.html

lightbox="true"

file="/images/gitops-promotions/tutorials/seq--policy-flow-yaml-view.png"

url="/images/gitops-promotions/tutorials/seq--policy-flow-yaml-view.png"

alt="YAML view of policy settings"

caption="YAML view of policy settings"

max-width="60%"

%}