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

Commitc15b1aa

Browse files
authored
Fix broken links (#1141)
* Fix broken links* Fix broken links
1 parent4f1a289 commitc15b1aa

File tree

7 files changed

+10
-203
lines changed

7 files changed

+10
-203
lines changed

‎_docs/installation/gitops/hosted-runtime.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -312,7 +312,7 @@ You have completed setting up your Hosted GitOps Runtime. You are ready to creat
312312
##(Optional) Create an Argo CD application
313313
Optional. Create an Argo CD application in Codefresh, deploy it to the cluster, and track deployment and performance in the Applications dashboard.
314314

315-
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/).
315+
1. Follow our[quick-start to create and deployanapplication]({{site.baseurl}}/docs/gitops-quick-start/products/create-app-ui/).
316316
OR
317317
Create your own application. See[Create an application]({{site.baseurl}}/docs/deployments/gitops/create-application/).
318318

‎_docs/products/promotion-flow-triggers.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ The Rollback flow triggers when the commit message contains terms like `revert`
131131
132132
As with other GitOps entities, you can configure Promotion Flow settings in either Form or YAML modes.
133133
134-
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/`.
134+
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/`.
135135
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)).
136136
137137
To configure directly in YAML, refer to our [Promotion Flow CRD](tbd) for the syntax requirements and descriptions.-->

‎_docs/products/promotion-version-properties.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -361,7 +361,7 @@ As with other GitOps entities, you can configure Promotion Settings for the prod
361361
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/`.
362362
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).
363363

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

366366
## Related articles
367367
[Assigning applications to products]({{site.baseurl}}/docs/products/assign-applications/)

‎_docs/promotions/create-promotion-sequence.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -66,15 +66,15 @@ enhance consistency, create reusable templates that apply across products.
6666
Create a product and connect related applications to it, either manually or declaratively.
6767

6868

69-
1.[Create promotion workflows]({{site.baseurl}}/docs/promotions/configuration/promotion-workflow/)
69+
1.[Create promotion workflows]({{site.baseurl}}/docs/promotions/entities/promotion-workflow/)
7070
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.
7171
Create Promotion Workflows (Argo Workflows) to implement any type of tests, validations, and custom requirements.
7272

73-
1.[Create policies to govern environment promotions]({{site.baseurl}}/docs/promotions/configuration/promotion-policy/)
73+
1.[Create policies to govern environment promotions]({{site.baseurl}}/docs/promotions/entities/promotion-policy/)
7474
Govern promotion behavior for environments by setting rules, checks, and validations that environments must meet before and after changes are promoted.
7575
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.
7676

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

‎_docs/promotions/entities/yaml.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ toc: true
88
Codefresh provides two options for defining manifests for promotion entities: Form mode and YAML mode.
99

1010
If you prefer working with YAML, create manifests for promotion entities using our YAML examples:
11-
*[Product YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/product-crd/)
12-
*[Promotion Template YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/promotion-template-crd/)
13-
*[Promotion Flow YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/promotion-flow-crd/)
14-
*[Promotion Policy YAML]({{site.baseurl}}/docs/promotions/configuration/yaml/promotion-policy-crd/)
11+
*[Product YAML]({{site.baseurl}}/docs/promotions/entities/yaml/product-crd/)
12+
*[Promotion Template YAML]({{site.baseurl}}/docs/promotions/entities/yaml/promotion-template-crd/)
13+
*[Promotion Flow YAML]({{site.baseurl}}/docs/promotions/entities/yaml/promotion-flow-crd/)
14+
*[Promotion Policy YAML]({{site.baseurl}}/docs/promotions/entities/yaml/promotion-policy-crd/)

‎_docs/quick-start/create-codefresh-account.md‎

Lines changed: 0 additions & 118 deletions
This file was deleted.

‎_docs/quick-start/promotions/create-product.md‎

Lines changed: 0 additions & 75 deletions
This file was deleted.

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp