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

Fix broken links#1141

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 intomasterfromfix-broken-links
Dec 31, 2024
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
2 changes: 1 addition & 1 deletion_docs/installation/gitops/hosted-runtime.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -312,7 +312,7 @@ You have completed setting up your Hosted GitOps Runtime. You are ready to creat
## (Optional) Create an Argo CD application
Optional. Create an Argo CD application in Codefresh, deploy it to the cluster, and track deployment and performance in the Applications dashboard.

1. Follow our quick-start to create and deploythe `codefresh-guestbook`application. Start with [Create application resources]({{site.baseurl}}/docs/quick-start/gitops-quick-start/create-app-specs/).
1. Follow our[quick-start to create and deployanapplication]({{site.baseurl}}/docs/gitops-quick-start/products/create-app-ui/).
OR
Create your own application. See [Create an application]({{site.baseurl}}/docs/deployments/gitops/create-application/).

Expand Down
16 changes: 8 additions & 8 deletions_docs/installation/gitops/shared-configuration.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -41,9 +41,9 @@ Here are a few types of configuration definitions stored in the Shared Configura
* [OAuth2]({{site.baseurl}}/docs/administration/account-user-management/oauth-setup/) authentication applications
* Manifests for promotion entities:
* [Products]({{site.baseurl}}/docs/products/configure-product-settings/)
* [Promotion Workflows]({{site.baseurl}}/docs/promotions/configuration/promotion-workflow)
* [Promotion Policies]({{site.baseurl}}/docs/promotions/configuration/promotion-policy/)
* [Promotion Flows]({{site.baseurl}}/docs/promotions/configuration/promotion-flow/)
* [Promotion Workflows]({{site.baseurl}}/docs/promotions/entities/promotion-workflow)
* [Promotion Policies]({{site.baseurl}}/docs/promotions/entities/promotion-policy/)
* [Promotion Flows]({{site.baseurl}}/docs/promotions/entities/promotion-flow/)
* [Promotion Templates]({{site.baseurl}}/docs/products/configure-product-settings/#configure-promotion-settings)

See [Shared Configuration Repo structure](#shared-configuration-repo-structure).
Expand DownExpand Up@@ -149,14 +149,14 @@ The `resources` directory contains the resources shared by _all_ clusters manage
| Shared Configuration Repo | Description |
| ---------- | -------- |
| `resources/all-runtimes-all-clusters` | Contains resource manifests applied to all the GitOps Runtimes in the account and to all the clusters managed by those Runtimes. In the above example, `manifest2.yaml` is applied to both `runtime1` and `runtime2`. |
|`resources/all-runtimes-all-clusters/promotion-workflows` | Stores manifests of Promotion Workflows, available to all Runtimes in the account.<br>See [Promotion Workflows]({{site.baseurl}}/docs/promotions/configuration/promotion-workflow). |
|`resources/all-runtimes-all-clusters/promotion-workflows` | Stores manifests of Promotion Workflows, available to all Runtimes in the account.<br>See [Promotion Workflows]({{site.baseurl}}/docs/promotions/entities/promotion-workflow). |
|`resources/control-planes` | Optional. When defined, applies every resource manifest to each Runtime’s `in-cluster`. Config map resources for example, when committed to this subdirectory, are deployed to each Runtime’s `in-cluster`. |
| `resources/app-projects` | Contains application project resources which control deployment destinations for applications. |
| `resources/configurations` | Contains platform-level resources which are Runtime-agnostic, essential for functionality related to product and promotion entities in GitOps. |
| `resources/configurations/products` |Contains manifests of product entities. All settings including source location for application version, promotable properties, promotion flows with trigger conditions if defined are saved. Note that applications assigned to products are not saved in the manifest. Product manifests are available to users with the required ABAC permissions. <br>See [Product Settings]({{site.baseurl}}/docs/products/configure-product-settings/) and [Product YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/product-crd/).|
| `resources/configurations/promotion-flows`| Contains manifests of promotion flows with the trigger and target environments, and custom promotion policy settings, if any.<br>See [Promotion Flow configuration]({{site.baseurl}}/docs/promotions/configuration/promotion-flow/) and [Promotion Flow YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/promotion-flow-crd/).|
|`resources/configurations/promotion-policies`| Contains manifests of promotion policies with the Pre- and Post-Action Workflows if defined, the Promotion Action, and target products and environments.<br>See [Promotion Policy configuration]({{site.baseurl}}/docs/promotions/configuration/promotion-policy/) and [Promotion Policy YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/product-crd/).|
|`resources/configurations/promotion-templates`| Contains manifests of promotion templates defining the sources for the release version and the properties to be promoted. <br>See [Promotion Template configuration]({{site.baseurl}}/docs/products/configure-product-settings/#configure-promotion-settings) and [Promotion Template YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/promotion-template-crd/).|
| `resources/configurations/products` |Contains manifests of product entities. All settings including source location for application version, promotable properties, promotion flows with trigger conditions if defined are saved. Note that applications assigned to products are not saved in the manifest. Product manifests are available to users with the required ABAC permissions. <br>See [Product Settings]({{site.baseurl}}/docs/products/configure-product-settings/) and [Product YAML]({{site.baseurl}}/docs/promotions/entities/yaml/product-crd/).|
| `resources/configurations/promotion-flows`| Contains manifests of promotion flows with the trigger and target environments, and custom promotion policy settings, if any.<br>See [Promotion Flow configuration]({{site.baseurl}}/docs/promotions/entities/promotion-flow/) and [Promotion Flow YAML]({{site.baseurl}}/docs/promotions/entities/yaml/promotion-flow-crd/).|
|`resources/configurations/promotion-policies`| Contains manifests of promotion policies with the Pre- and Post-Action Workflows if defined, the Promotion Action, and target products and environments.<br>See [Promotion Policy configuration]({{site.baseurl}}/docs/promotions/entities/promotion-policy/) and [Promotion Policy YAML]({{site.baseurl}}/docs/promotions/entities/yaml/product-crd/).|
|`resources/configurations/promotion-templates`| Contains manifests of promotion templates defining the sources for the release version and the properties to be promoted. <br>See [Promotion Template configuration]({{site.baseurl}}/docs/products/configure-product-settings/#configure-promotion-settings) and [Promotion Template YAML]({{site.baseurl}}/docs/promotions/entities/yaml/promotion-template-crd/).|
|`resources/runtimes/<runtime_name>`| Optional. Runtime-specific subdirectory. Every resource manifest in a runtime-specific subdirectory is applied to only the GitOps Runtime defined by `<runtime_name>`. In the above example, `manifest4.yaml` is applied only to `runtime1`, and `manifest5.yaml` is applied only to `runtime2`. |


Expand Down
2 changes: 1 addition & 1 deletion_docs/products/configure-product-settings.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -36,7 +36,7 @@ The path in the Shared Configuration Repo is `<gitops-runtime>/<shared-configura

See [Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/) and [Designating Configuration Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#designating-configuration-runtimes).

For the YAML specifications, see [Product YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/product-crd/) and [Promotion Template YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/promotion-template-crd/).
For the YAML specifications, see [Product YAML]({{site.baseurl}}/docs/promotions/entities/yaml/product-crd/) and [Promotion Template YAML]({{site.baseurl}}/docs/promotions/entities/yaml/promotion-template-crd/).



Expand Down
4 changes: 2 additions & 2 deletions_docs/products/promotion-flow-triggers.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -30,7 +30,7 @@ You can select multiple Promotion Flows for a product, and customize the conditi

##### Where can you configure Promotion Flows and triggers?
In Product > Settings > Promotion Flows, you can select one or more Promotion Flows for the product, and then configure custom conditions to trigger the flows.
See also [Promotion Flow CRD]({{site.baseurl}}/docs/promotions/configuration/yaml/promotion-flow-crd/).
See also [Promotion Flow CRD]({{site.baseurl}}/docs/promotions/entities/yaml/promotion-flow-crd/).


{% include
Expand DownExpand Up@@ -131,7 +131,7 @@ The Rollback flow triggers when the commit message contains terms like `revert`

As with other GitOps entities, you can configure Promotion Flow settings in either Form or YAML modes.

Once configured and committed, these settings are saved as the `promotion-flow` resource within the Shared Configuration Repository in the GitOps Runtime selected as the Configuration Runtime. The path in the Shared Configuration Repo is `<gitops-runtime>/<shared-configuration-repo>/resources/configuration/promotion-flows/`.
Once configured and committed, these settings are saved as the `promotion-flow` resource within the Shared Configuration Repository in the GitOps Runtime selected as the Configuration Runtime. The path in the Shared Configuration Repo is `<gitops-runtime>/<shared-configuration-repo>/resources/entities/promotion-flows/`.
See [Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/) and [Designating Configuration Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#designating-configuration-runtimes)).

To configure directly in YAML, refer to our [Promotion Flow CRD](tbd) for the syntax requirements and descriptions. -->
Expand Down
2 changes: 1 addition & 1 deletion_docs/products/promotion-version-properties.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -361,7 +361,7 @@ As with other GitOps entities, you can configure Promotion Settings for the prod
When you define an Inline template, configure and commit the settings, they are saved as a `promotion-template` resource within the Shared Configuration Repository in the GitOps Runtime selected as the Configuration Runtime. The path in the Shared Configuration Repo is `<gitops-runtime>/<shared-configuration-repo>/resources/configuration/promotion-templates/`.
See [Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/) and [Designating Configuration Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#designating-configuration-runtimes).

To configure directly in YAML, refer to our [Promotion Template YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/promotion-template-crd/).
To configure directly in YAML, refer to our [Promotion Template YAML]({{site.baseurl}}/docs/promotions/entities/yaml/promotion-template-crd/).

## Related articles
[Assigning applications to products]({{site.baseurl}}/docs/products/assign-applications/)
Expand Down
6 changes: 3 additions & 3 deletions_docs/promotions/create-promotion-sequence.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -66,15 +66,15 @@ enhance consistency, create reusable templates that apply across products.
Create a product and connect related applications to it, either manually or declaratively.


1. [Create promotion workflows]({{site.baseurl}}/docs/promotions/configuration/promotion-workflow/)
1. [Create promotion workflows]({{site.baseurl}}/docs/promotions/entities/promotion-workflow/)
As part of promoting changes across environments, it's customary to run tests and validations that match the requirements of the target environments in the promotion sequence. For example, create workflows that run smoke tests to verify basic functionality or database validation checks to ensure data integrity.
Create Promotion Workflows (Argo Workflows) to implement any type of tests, validations, and custom requirements.

1. [Create policies to govern environment promotions]({{site.baseurl}}/docs/promotions/configuration/promotion-policy/)
1. [Create policies to govern environment promotions]({{site.baseurl}}/docs/promotions/entities/promotion-policy/)
Govern promotion behavior for environments by setting rules, checks, and validations that environments must meet before and after changes are promoted.
Promotion Policies allow you to define these rules by combining Promotion Workflows and the promotion action based on environment type, product, or other criteria. When a promotion is triggered for an environment, the policy mechanism merges settings from all relevant global policies according to priority, providing automated governance for consistent and reliable promotion behavior.

1. [Create promotion flows to orchestrate promotions]({{site.baseurl}}/docs/promotions/configuration/promotion-flow/)
1. [Create promotion flows to orchestrate promotions]({{site.baseurl}}/docs/promotions/entities/promotion-flow/)
Orchestrate the sequence of actions to move and deploy changes through the required environments, from the trigger environment to the final target environment.
Promotion Flows ensure that changes are promoted in a controlled and predictable manner by integrating environments, products and applications, promotion workflows, and policies.

Expand Down
4 changes: 2 additions & 2 deletions_docs/promotions/entities/promotion-workflow.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -367,8 +367,8 @@ max-width="60%"


## Related articles
[Configure Promotion Flows]({{site.baseurl}}/docs/promotions/configuration/promotion-flow/)
[Configure Promotion Policies]({{site.baseurl}}/docs/promotions/configuration/promotion-policy/)
[Configure Promotion Flows]({{site.baseurl}}/docs/promotions/entities/promotion-flow/)
[Configure Promotion Policies]({{site.baseurl}}/docs/promotions/entities/promotion-policy/)
[Trigger promotions]({{site.baseurl}}/docs/promotions/trigger-promotions/)
[Tracking product releases]({{site.baseurl}}/docs/promotions/product-releases/)
[Promotion sequences]({{site.baseurl}}/docs/promotions/create-promotion-sequence/)
Expand Down
8 changes: 4 additions & 4 deletions_docs/promotions/entities/yaml.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -8,7 +8,7 @@ toc: true
Codefresh provides two options for defining manifests for promotion entities: Form mode and YAML mode.

If you prefer working with YAML, create manifests for promotion entities using our YAML examples:
* [Product YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/product-crd/)
* [Promotion Template YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/promotion-template-crd/)
* [Promotion Flow YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/promotion-flow-crd/)
* [Promotion Policy YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/promotion-policy-crd/)
* [Product YAML]({{site.baseurl}}/docs/promotions/entities/yaml/product-crd/)
* [Promotion Template YAML]({{site.baseurl}}/docs/promotions/entities/yaml/promotion-template-crd/)
* [Promotion Flow YAML]({{site.baseurl}}/docs/promotions/entities/yaml/promotion-flow-crd/)
* [Promotion Policy YAML]({{site.baseurl}}/docs/promotions/entities/yaml/promotion-policy-crd/)
Loading
[8]ページ先頭
©2009-2025 Movatter.jp