You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/promotions/product-promotion-props.md
+4-8Lines changed: 4 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,14 +48,14 @@ max-width="60%"
48
48
49
49
The product version defines the source from which the application version is retrieved and promoted.
50
50
51
-
####Why is this important?
51
+
#####Why is this important?
52
52
53
53
Defining the version source ensures that each promotion consistently targets the correct version, reducing the risk of mismatches, maintaining application integrity, and providing a traceable version history.
54
54
55
55
>**NOTE**
56
56
The Environments, Product, and GitOps Apps dashboards display product versions**only for Helm-based applications**. For other types, versions are not displayed—even if configured.
57
57
58
-
####Version Attribute
58
+
#####Version Attribute
59
59
60
60
The version is defined using a JSON path expression, relative to the`spec.source.repoURL` and`spec.source.path` attributes in the application's manifest.
61
61
Review[examples of version attributes]({{site.baseurl}}/docs/products/promotion-version-properties/#examples-of-version-attributes).
@@ -80,9 +80,6 @@ For details, see [Configuring properties for promotion across applications]({{si
80
80
81
81
82
82
83
-
84
-
85
-
86
83
##Concurrent promotion behavior for product
87
84
88
85
Promotion flows can be triggered either automatically or manually, which may lead to multiple promotions being activated for the same product.
@@ -104,9 +101,9 @@ For details, see [Configuring promotion concurrency for products]({{site.baseurl
104
101
105
102
Assign predefined Promotion Flows to a product and configure the triggers that initiate each flow based on specific conditions.
106
103
107
-
####Why is this important?
104
+
#####Why is this important?
108
105
109
-
Assigning flows and defining their triggersensures that changes are promoted under the right conditions,reduces manual work improving automation for a more reliable promotion process.
106
+
Assigning flows and defining their triggersensure that changesto the productare promoted under the right conditions,and improves automation for a more reliable promotion process.
110
107
111
108
{% include
112
109
image.html
@@ -119,7 +116,6 @@ Assigning flows and defining their triggers ensures that changes are promoted un