Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Update product-promotion-props.md#1297

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
NimRegev merged 4 commits intomasterfromgotops-toc-proxy-fix
Apr 27, 2025
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions_docs/promotions/product-promotion-props.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -48,14 +48,14 @@ max-width="60%"

The product version defines the source from which the application version is retrieved and promoted.

#### Why is this important?
##### Why is this important?

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.

> **NOTE**
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.

#### Version Attribute
##### Version Attribute

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.
Review [examples of version attributes]({{site.baseurl}}/docs/products/promotion-version-properties/#examples-of-version-attributes).
Expand All@@ -80,9 +80,6 @@ For details, see [Configuring properties for promotion across applications]({{si






## Concurrent promotion behavior for product

Promotion flows can be triggered either automatically or manually, which may lead to multiple promotions being activated for the same product.
Expand All@@ -104,9 +101,9 @@ For details, see [Configuring promotion concurrency for products]({{site.baseurl

Assign predefined Promotion Flows to a product and configure the triggers that initiate each flow based on specific conditions.

#### Why is this important?
##### Why is this important?

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.
Assigning flows and defining their triggersensure that changesto the productare promoted under the right conditions,and improves automation for a more reliable promotion process.

{% include
image.html
Expand All@@ -119,7 +116,6 @@ Assigning flows and defining their triggers ensures that changes are promoted un
%}



## Related articles
[Configure Product Settings]({{site.baseurl}}/docs/products/configure-product-settings/)
[Create products]({{site.baseurl}}/docs/products/create-product/)
1 change: 0 additions & 1 deletion_gitops/promotions/entities.md
View file
Open in desktop

This file was deleted.

[8]ページ先頭
©2009-2025 Movatter.jp