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 argument descriptions#1147

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 2 commits intomasterfromgitops-branch-param-promo-workflow
Jan 6, 2025
Merged
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
11 changes: 6 additions & 5 deletions_docs/promotions/entities/promotion-workflow.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -99,13 +99,13 @@ At the simplest levels, you can display the values from the parameters in notifi
|`APP_NAMESPACE` | The namespace where the application is deployed to. For example, `gitops`. | ✅ | ✅ |
|`APP_NAME` | The name of the specific application the Promotion Workflows and the Promotion Action pertain to. For example, `trioapp-staging`.| ✅ | ✅ |
| `REPO_URL` | The Git repository with the application settings, as defined in the application's configuration. See [Source settings for applications]({{site.baseurl}}/docs/deployments/gitops/create-application/#sources).| ✅ | ✅ |
| `BRANCH` | The specific Git branch to which to promote changes. For example, `main`.|✅ | ✅ |
| `BRANCH` | The specific Git branch to which to promote changes, retrieved from `spec.source.targetRevision` defined in the application's configuration settings. <br>If `spec.source.targetRevision` is set to `HEAD`, this is the value used for `BRANCH` in both the Pre- and Post-Action Workflows, even if the resolved branch name is `main`, `master`, or any custom name.|✅ | ✅ |
| `PATH` | The relative path within the repository defined by `REPO_URL` to the directory or file containing the application's configuration. See [Source settings for applications]({{site.baseurl}}/docs/deployments/gitops/create-application/#sources). | ✅ | ✅ |
|`RUNTIME` |The name of the GitOps Runtime the application being promoted is associated with. |✅ | ✅ |
|`COMMIT_SHA`| The unique identifier (SHA) of the commit, generated by Git, including the precise set of changes addressed by the commit. Can be used as a trigger condition in Promotion Flows configured for a product. | |✅ |
|`COMMIT_AUTHOR`| The name of the user who made the commit. Useful for tracking changes and for notifications.| | ✅ |
|`COMMIT-MESSAGE` | The text in the commit message associated with the code change that triggered the promotion, providing context for the changes introduced by the commit. | |✅ |
|`COMMIT-DATE` | The date and time when the commit was made. Useful to correlate the commit with other events and understand the timeline of changes.| | ✅ |
|`COMMIT_SHA`| The unique identifier (SHA) of the commit, generated by Git, including the precise set of changes addressed by the commit. Can be used as a trigger condition in Promotion Flows configured for a product.<br>Available in Post-Action Workflows only for commit-based Promotion Actions. Not available for PR-based Promotion Actions. | |✅ |
|`COMMIT_AUTHOR`| The name of the user who made the commit. Useful for tracking changes and for notifications.<br>Available in Post-Action Workflows only for commit-based Promotion Actions. Not available for PR-based Promotion Actions.| | ✅ |
|`COMMIT-MESSAGE` | The text in the commit message associated with the code change that triggered the promotion, providing context for the changes introduced by the commit.<br>Available in Post-Action Workflows only for commit-based Promotion Actions. Not available for PR-based Promotion Actions. | |✅ |
|`COMMIT-DATE` | The date and time when the commit was made. Useful to correlate the commit with other events and understand the timeline of changes.<br>Available in Post-Action Workflows only for commit-based Promotion Actions. Not available for PR-based Promotion Actions.| | ✅ |


### Custom global parameters
Expand All@@ -125,6 +125,7 @@ outputs:
See this [example](#example-3-pre--and-post-action-workflows-with-custom-globalname-argument-usage) that uses the `globalName` argument.


###



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