Configure product promotion settings & flows
Configure key settings for the product to optimize promotion
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 product’s version, properties to be promoted, and Promotion Flows for a consistent promotion experience.
Defining sources for product versions and properties
Product version for promotion
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.
NOTE
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.
Version attribute
The Version attribute 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.
Product properties for promotion
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.
Property attributes
You can define multiple files, or multiple attributes within the same file at any level, as properties to be promoted. Review examples of promotable properties.
JSON path expressions
Both the version source and the properties to be promoted are defined through JSON path expressions.
For details, see Configuring app version and promotable properties.
Assigning a Promotion Flow and defining its triggers
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.
For details, see Configuring promotion flows and triggers.