[doc] Add links to pipectl init from the pages of configuring ECS/K…

…8s App (#4802) * Add link to pipectl init from the page of configuring ECS app Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> * Add link to pipectl init from the page of configuring Kubernetes app Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> * Fix the title to 'Note' Signed-off-by: t-kikuc <tkikuchi07f@gmail.com> --------- Signed-off-by: t-kikuc <tkikuchi07f@gmail.com>
pipe-cd · Mar 20, 2024 · 1a60f84 · 1a60f84
1 parent 1478d75
commit 1a60f84
Show file tree

Hide file tree

Showing 4 changed files with 20 additions and 0 deletions.
diff --git a/...t/en/docs-dev/user-guide/managing-application/defining-app-configuration/ecs.md b/...t/en/docs-dev/user-guide/managing-application/defining-app-configuration/ecs.md
@@ -19,6 +19,11 @@ To deploy your application to run continuously or to place it behind a load bala
 
 If you're not familiar with ECS, you can get examples for those files from [here](../../../../examples/#ecs-applications).
 
+Note:
+
+You can generate an application config file easily and interactively by [`pipectl init`](../../command-line-tool.md#generating-an-application-config-apppipecdyaml).
+
+
 ## Quick sync
 
 By default, when the [pipeline](../../../configuration-reference/#ecs-application) was not specified, PipeCD triggers a quick sync deployment for the merged pull request.

diff --git a/...cs-dev/user-guide/managing-application/defining-app-configuration/kubernetes.md b/...cs-dev/user-guide/managing-application/defining-app-configuration/kubernetes.md
@@ -8,6 +8,11 @@ description: >
 
 Based on the application configuration and the pull request changes, PipeCD plans how to execute the deployment: doing quick sync or doing progressive sync with the specified pipeline.
 
+Note:
+
+You can generate an application config file easily and interactively by [`pipectl init`](../../command-line-tool.md#generating-an-application-config-apppipecdyaml).
+
+
 ## Quick sync
 
 Quick sync is a fast way to sync application to the state specified in the target Git commit without any progressive strategy. It just applies all the defined manifiests to sync the application.

diff --git a/.../docs-v0.46.x/user-guide/managing-application/defining-app-configuration/ecs.md b/.../docs-v0.46.x/user-guide/managing-application/defining-app-configuration/ecs.md
@@ -19,6 +19,11 @@ To deploy your application to run continuously or to place it behind a load bala
 
 If you're not familiar with ECS, you can get examples for those files from [here](../../../../examples/#ecs-applications).
 
+Note:
+
+You can generate an application config file easily and interactively by [`pipectl init`](../../command-line-tool.md#generating-an-application-config-apppipecdyaml).
+
+
 ## Quick sync
 
 By default, when the [pipeline](../../../configuration-reference/#ecs-application) was not specified, PipeCD triggers a quick sync deployment for the merged pull request.

diff --git a/...0.46.x/user-guide/managing-application/defining-app-configuration/kubernetes.md b/...0.46.x/user-guide/managing-application/defining-app-configuration/kubernetes.md
@@ -8,6 +8,11 @@ description: >
 
 Based on the application configuration and the pull request changes, PipeCD plans how to execute the deployment: doing quick sync or doing progressive sync with the specified pipeline.
 
+Note:
+
+You can generate an application config file easily and interactively by [`pipectl init`](../../command-line-tool.md#generating-an-application-config-apppipecdyaml).
+
+
 ## Quick sync
 
 Quick sync is a fast way to sync application to the state specified in the target Git commit without any progressive strategy. It just applies all the defined manifiests to sync the application.