Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gitops promotion policy #1019

Closed
wants to merge 12 commits into from
Closed

Gitops promotion policy #1019

wants to merge 12 commits into from

Conversation

NimRegev
Copy link
Contributor

No description provided.

@codefresh-git-integration
Copy link

Added promotion policy entry to nav yaml
@codefresh-git-integration
Copy link

@codefresh-git-integration
Copy link

@codefresh-git-integration
Copy link

_docs/promotions/promotion-policy.md Outdated Show resolved Hide resolved
_docs/promotions/promotion-policy.md Outdated Show resolved Hide resolved
_docs/promotions/promotion-policy.md Outdated Show resolved Hide resolved
|**Name** | The name of the Promotion Policy.<br>The name must be unique in the cluster, and must match Kubernetes naming conventions. |
|**Promotion Settings** | The settings that comprise the Promotion Policy.<br>{::nomarkdown} <ul><li><b>Pre-Action Workflow</b>: Optional. The Promotion Workflow to run before the Promotion Action. </li><li><b>Action</b>Required. The Promotion Action to update the target application's source repository.<ul><li><b>Commit</b>: Perform a Git commit on the source repository. Commits are implemented immediately without not requiring manual approval to move to the next stage of the Promotion Policy.</li><li><b>Pull Request</b>: Open a pull request (PR) on the change to the source repository. Depending on your PR policy, this option may require manual approval to move to the nex stage.</li><li><b>No Action</b>: Run the selected Pre-Action Workflow, and the Post-Action Workflow if any, without performing a commit or opening a pull request on the application's source repository.<br>No Action requires a Pre-Action Workflow to be selected that includes a step to automatically execute the action to promote the target application. Otherwise, Promotion Flows will fail. <br>This option is useful to run custom promotion policy mechanisms, not involving updating the target application's source repository to promote the application.<br></li></ul>{:/}See [Promotion Workflows]({{site.baseurl}}/docs/promotions/promotion-workflow/).|
|**Products** |Single or multiple Products to which to apply the Promotion Policy. If target Environments are not defined, at least one Product is required. {::nomarkdown}<ul><li><b>Product</b>: Match Products by the name or names defined. </li><li><b>Tags</b>: Match Products by the tag or tags defined.</li></ul>{:/}|
|**Environments** |Single or multiple Environments to which to apply the Promotion Policy. If target Products are not defined, at least one Environment is required.{::nomarkdown}<ul><li><b>Kind</b>: Match Environments by their type, either <b>Pre-production</b> or <b>Production</b>.</li><li><b> Environment</b>: Match Environments by the name or names defined.</li><li><b>Tags</b>: Match Environments by the tag or tags defined. </li></ul>{:/}|

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

_docs/promotions/promotion-policy.md Outdated Show resolved Hide resolved
Implemented review comments from Denis
@codefresh-git-integration
Copy link

Updated content and added screenshots
@codefresh-git-integration
Copy link

@NimRegev NimRegev closed this Sep 18, 2024
@NimRegev
Copy link
Contributor Author

Merged with gitops-promotion-flow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants