url:"/promotion-policy"

-title:Promotion Workflows

url:"/promotion-workflow"

-title:Customize product promotion settings

-title:Product promotion settings

url:"/product-promotion-props"

-title:Promotion entity YAMLs

url:"/yaml"

toc:true

Promotion settings for products define the configurations that determine which promotion sequences are valid based on changes to the product, the conditions under which to initiate them, and the exact changes to promote. These settings ensure consistent, accurate, and reliable delivery of updates across environments.

Before or after configuring specializedpromotionentities such as Promotion Flows, Policies, and Workflows, note that there are product-specific settings crucialtoeffective, reliable promotions, regardless ofthemethod you use or intend to use.

By automating these configurations,promotionsettings by product reduce manual effort, minimize errors, and align with your deployment strategytoensure that changes are deployed undertheright conditions.

If you've created products, make sure you have configured the product's version, properties to be promoted, and Promotion Flows for a consistent promotion experience.

* Product version (for Helm-based applications)

* Properties to promote

* Promotion Flows and their triggers

{% include

image.html

max-width="60%"

%}

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.

The product version specifies the source of the version you want to promote.

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

Defining a source for theproductversion ensures that each promotion action consistently targets the correct version of your product's applications.This minimizes risks associated with version mismatches, maintains application integrity, and provides a traceable version history.

The Environments, Product, and GitOps Apps dashboards display the product version_only for Helm application types_.

For other application types, product versions are not displayed even if configured.

The Environments, Product, and GitOps Apps dashboards display the product version_only for Helm application types_. For other application types, product versions are not displayed versions even when configured.

The Version attributeis relative to the`spec.source.repoURL` and`spec.source.path` attributes defined in the source application's configuration manifest.

The Version attribute, defined as a JSON path expression,is relative to the`spec.source.repoURL` and`spec.source.path` attributes defined in the source application's configuration manifest.

Review[examples of version attributes]({{site.baseurl}}/docs/products/promotion-version-properties/#examples-of-version-attributes).

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.

For details, see[Configuring versions for promoted applications]({{site.baseurl}}/docs/docs/products/promotion-version-properties/).

Product properties specifies the files and precise attributes—such as tags, version numbers, or other application attributes—to promote across environments.

Configuringtheseproperties combines precision with automation,enabling promotionsthat consistently meet your defined requirements.

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

Configuring properties combines precision with automation,ensuringthat promotions consistently meet your defined requirements.

Defining properties to be promoted for productssimplifies cross-environment promotions, enforces deployment standards, and enables targeted updates.

You can define multiple files, ormultipleattributes withinthe samefile at any level, as propertiesto be promoted.

You can define multiple files, or attributes withinafile at any level,through JSON path expressions,as propertiesfor promotion.

Review[examples of promotable properties]({{site.baseurl}}/docs/products/promotion-version-properties/#examples-of-properties-for-promotion).

Both the version source and the properties to be promoted are defined through[JSON path expressions](#json-path-expressions-for-files-and-attributes).

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 one or more flows 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 predefined conditions, such as matching commit messages or specific code changes.

By assigning Promotion Flows and defining triggers, you reduce manual input, streamline automation, and ensure that changes are promoted in alignment with predefined conditions. This results in a more efficient and reliable promotion process.

{% include