From 803f23e8a0452f44a4c61357e229959ca4cfda12 Mon Sep 17 00:00:00 2001 From: e-esakman Date: Tue, 28 Apr 2026 20:12:58 +0530 Subject: [PATCH 1/3] docs: fix typos in script-run and installation docs Signed-off-by: e-esakman --- .../install-control-plane/installing-controlplane-on-k8s.md | 2 +- .../managing-application/customizing-deployment/script-run.md | 4 ++-- .../en/docs-v0.39.x/installation/install-controlplane.md | 2 +- .../en/docs-v0.40.x/installation/install-controlplane.md | 2 +- .../en/docs-v0.41.x/installation/install-controlplane.md | 2 +- .../en/docs-v0.42.x/installation/install-controlplane.md | 2 +- .../en/docs-v0.43.x/installation/install-controlplane.md | 2 +- .../en/docs-v0.44.x/installation/install-controlplane.md | 2 +- .../install-control-plane/installing-controlplane-on-k8s.md | 2 +- .../managing-application/customizing-deployment/script-run.md | 2 +- .../install-control-plane/installing-controlplane-on-k8s.md | 2 +- .../managing-application/customizing-deployment/script-run.md | 2 +- .../install-control-plane/installing-controlplane-on-k8s.md | 2 +- .../managing-application/customizing-deployment/script-run.md | 4 ++-- .../install-control-plane/installing-controlplane-on-k8s.md | 2 +- .../managing-application/customizing-deployment/script-run.md | 4 ++-- .../install-control-plane/installing-controlplane-on-k8s.md | 2 +- .../managing-application/customizing-deployment/script-run.md | 4 ++-- .../install-control-plane/installing-controlplane-on-k8s.md | 2 +- .../managing-application/customizing-deployment/script-run.md | 4 ++-- .../install-control-plane/installing-controlplane-on-k8s.md | 2 +- .../managing-application/customizing-deployment/script-run.md | 4 ++-- .../install-control-plane/installing-controlplane-on-k8s.md | 2 +- .../managing-application/customizing-deployment/script-run.md | 4 ++-- .../install-control-plane/installing-controlplane-on-k8s.md | 2 +- .../managing-application/customizing-deployment/script-run.md | 4 ++-- .../install-control-plane/installing-controlplane-on-k8s.md | 2 +- .../managing-application/customizing-deployment/script-run.md | 4 ++-- 28 files changed, 37 insertions(+), 37 deletions(-) diff --git a/docs/content/en/docs-dev/installation/install-control-plane/installing-controlplane-on-k8s.md b/docs/content/en/docs-dev/installation/install-control-plane/installing-controlplane-on-k8s.md index cb4578b88f..768ddd2561 100644 --- a/docs/content/en/docs-dev/installation/install-control-plane/installing-controlplane-on-k8s.md +++ b/docs/content/en/docs-dev/installation/install-control-plane/installing-controlplane-on-k8s.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-dev/user-guide/managing-application/customizing-deployment/script-run.md b/docs/content/en/docs-dev/user-guide/managing-application/customizing-deployment/script-run.md index 6811282691..4c835a5261 100644 --- a/docs/content/en/docs-dev/user-guide/managing-application/customizing-deployment/script-run.md +++ b/docs/content/en/docs-dev/user-guide/managing-application/customizing-deployment/script-run.md @@ -93,13 +93,13 @@ For example, If you are using the container platform and the offcial piped conta The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX commands available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). -If you want to use your commands, you can realize it with either step below. +If you want to use your commands, you can do that with either of the following steps. - Prepare your own environment container image then add [piped binary](https://github.com/pipe-cd/pipecd/releases) to it. - Build your own container image based on `ghcr.io/pipe-cd/piped` image. ## Default environment values -You can use the envrionment values related to the deployment. +You can use the environment values related to the deployment. | Name | Description | Example | |-|-|-| diff --git a/docs/content/en/docs-v0.39.x/installation/install-controlplane.md b/docs/content/en/docs-v0.39.x/installation/install-controlplane.md index 6cb214ac56..e91256208f 100644 --- a/docs/content/en/docs-v0.39.x/installation/install-controlplane.md +++ b/docs/content/en/docs-v0.39.x/installation/install-controlplane.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.40.x/installation/install-controlplane.md b/docs/content/en/docs-v0.40.x/installation/install-controlplane.md index 6cb214ac56..e91256208f 100644 --- a/docs/content/en/docs-v0.40.x/installation/install-controlplane.md +++ b/docs/content/en/docs-v0.40.x/installation/install-controlplane.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.41.x/installation/install-controlplane.md b/docs/content/en/docs-v0.41.x/installation/install-controlplane.md index 6cb214ac56..e91256208f 100644 --- a/docs/content/en/docs-v0.41.x/installation/install-controlplane.md +++ b/docs/content/en/docs-v0.41.x/installation/install-controlplane.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.42.x/installation/install-controlplane.md b/docs/content/en/docs-v0.42.x/installation/install-controlplane.md index 6cb214ac56..e91256208f 100644 --- a/docs/content/en/docs-v0.42.x/installation/install-controlplane.md +++ b/docs/content/en/docs-v0.42.x/installation/install-controlplane.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.43.x/installation/install-controlplane.md b/docs/content/en/docs-v0.43.x/installation/install-controlplane.md index 6cb214ac56..e91256208f 100644 --- a/docs/content/en/docs-v0.43.x/installation/install-controlplane.md +++ b/docs/content/en/docs-v0.43.x/installation/install-controlplane.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.44.x/installation/install-controlplane.md b/docs/content/en/docs-v0.44.x/installation/install-controlplane.md index 6cb214ac56..e91256208f 100644 --- a/docs/content/en/docs-v0.44.x/installation/install-controlplane.md +++ b/docs/content/en/docs-v0.44.x/installation/install-controlplane.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.45.x/installation/install-control-plane/installing-controlplane-on-k8s.md b/docs/content/en/docs-v0.45.x/installation/install-control-plane/installing-controlplane-on-k8s.md index b41a8c71bd..64e7ad0709 100644 --- a/docs/content/en/docs-v0.45.x/installation/install-control-plane/installing-controlplane-on-k8s.md +++ b/docs/content/en/docs-v0.45.x/installation/install-control-plane/installing-controlplane-on-k8s.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.46.x/user-guide/managing-application/customizing-deployment/script-run.md b/docs/content/en/docs-v0.46.x/user-guide/managing-application/customizing-deployment/script-run.md index 5acacf2936..900d23d807 100644 --- a/docs/content/en/docs-v0.46.x/user-guide/managing-application/customizing-deployment/script-run.md +++ b/docs/content/en/docs-v0.46.x/user-guide/managing-application/customizing-deployment/script-run.md @@ -96,7 +96,7 @@ For example, If you are using the container platform and the offcial piped conta The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX commands available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). -If you want to use your commands, you can realize it with either step below. +If you want to use your commands, you can do that with either of the following steps. - Prepare your own environment container image then add [piped binary](https://github.com/pipe-cd/pipecd/releases) to it. - Build your own container image based on `ghcr.io/pipe-cd/piped` image. diff --git a/docs/content/en/docs-v0.47.x/installation/install-control-plane/installing-controlplane-on-k8s.md b/docs/content/en/docs-v0.47.x/installation/install-control-plane/installing-controlplane-on-k8s.md index b41a8c71bd..64e7ad0709 100644 --- a/docs/content/en/docs-v0.47.x/installation/install-control-plane/installing-controlplane-on-k8s.md +++ b/docs/content/en/docs-v0.47.x/installation/install-control-plane/installing-controlplane-on-k8s.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.47.x/user-guide/managing-application/customizing-deployment/script-run.md b/docs/content/en/docs-v0.47.x/user-guide/managing-application/customizing-deployment/script-run.md index 705ffcfecb..22dc3bc569 100644 --- a/docs/content/en/docs-v0.47.x/user-guide/managing-application/customizing-deployment/script-run.md +++ b/docs/content/en/docs-v0.47.x/user-guide/managing-application/customizing-deployment/script-run.md @@ -92,7 +92,7 @@ For example, If you are using the container platform and the offcial piped conta The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX commands available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). -If you want to use your commands, you can realize it with either step below. +If you want to use your commands, you can do that with either of the following steps. - Prepare your own environment container image then add [piped binary](https://github.com/pipe-cd/pipecd/releases) to it. - Build your own container image based on `ghcr.io/pipe-cd/piped` image. diff --git a/docs/content/en/docs-v0.48.x/installation/install-control-plane/installing-controlplane-on-k8s.md b/docs/content/en/docs-v0.48.x/installation/install-control-plane/installing-controlplane-on-k8s.md index b41a8c71bd..64e7ad0709 100644 --- a/docs/content/en/docs-v0.48.x/installation/install-control-plane/installing-controlplane-on-k8s.md +++ b/docs/content/en/docs-v0.48.x/installation/install-control-plane/installing-controlplane-on-k8s.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.48.x/user-guide/managing-application/customizing-deployment/script-run.md b/docs/content/en/docs-v0.48.x/user-guide/managing-application/customizing-deployment/script-run.md index 2024a8760e..de6d24102c 100644 --- a/docs/content/en/docs-v0.48.x/user-guide/managing-application/customizing-deployment/script-run.md +++ b/docs/content/en/docs-v0.48.x/user-guide/managing-application/customizing-deployment/script-run.md @@ -93,13 +93,13 @@ For example, If you are using the container platform and the offcial piped conta The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX commands available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). -If you want to use your commands, you can realize it with either step below. +If you want to use your commands, you can do that with either of the following steps. - Prepare your own environment container image then add [piped binary](https://github.com/pipe-cd/pipecd/releases) to it. - Build your own container image based on `ghcr.io/pipe-cd/piped` image. ## Default environment values -You can use the envrionment values related to the deployment. +You can use the environment values related to the deployment. | Name | Description | Example | |-|-|-| diff --git a/docs/content/en/docs-v0.49.x/installation/install-control-plane/installing-controlplane-on-k8s.md b/docs/content/en/docs-v0.49.x/installation/install-control-plane/installing-controlplane-on-k8s.md index b41a8c71bd..64e7ad0709 100644 --- a/docs/content/en/docs-v0.49.x/installation/install-control-plane/installing-controlplane-on-k8s.md +++ b/docs/content/en/docs-v0.49.x/installation/install-control-plane/installing-controlplane-on-k8s.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.49.x/user-guide/managing-application/customizing-deployment/script-run.md b/docs/content/en/docs-v0.49.x/user-guide/managing-application/customizing-deployment/script-run.md index dd4ba0544f..4785d2c707 100644 --- a/docs/content/en/docs-v0.49.x/user-guide/managing-application/customizing-deployment/script-run.md +++ b/docs/content/en/docs-v0.49.x/user-guide/managing-application/customizing-deployment/script-run.md @@ -93,13 +93,13 @@ For example, If you are using the container platform and the offcial piped conta The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX commands available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). -If you want to use your commands, you can realize it with either step below. +If you want to use your commands, you can do that with either of the following steps. - Prepare your own environment container image then add [piped binary](https://github.com/pipe-cd/pipecd/releases) to it. - Build your own container image based on `ghcr.io/pipe-cd/piped` image. ## Default environment values -You can use the envrionment values related to the deployment. +You can use the environment values related to the deployment. | Name | Description | Example | |-|-|-| diff --git a/docs/content/en/docs-v0.50.x/installation/install-control-plane/installing-controlplane-on-k8s.md b/docs/content/en/docs-v0.50.x/installation/install-control-plane/installing-controlplane-on-k8s.md index b41a8c71bd..64e7ad0709 100644 --- a/docs/content/en/docs-v0.50.x/installation/install-control-plane/installing-controlplane-on-k8s.md +++ b/docs/content/en/docs-v0.50.x/installation/install-control-plane/installing-controlplane-on-k8s.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.50.x/user-guide/managing-application/customizing-deployment/script-run.md b/docs/content/en/docs-v0.50.x/user-guide/managing-application/customizing-deployment/script-run.md index 69f0e20485..3c08c3dbf2 100644 --- a/docs/content/en/docs-v0.50.x/user-guide/managing-application/customizing-deployment/script-run.md +++ b/docs/content/en/docs-v0.50.x/user-guide/managing-application/customizing-deployment/script-run.md @@ -93,13 +93,13 @@ For example, If you are using the container platform and the offcial piped conta The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX commands available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). -If you want to use your commands, you can realize it with either step below. +If you want to use your commands, you can do that with either of the following steps. - Prepare your own environment container image then add [piped binary](https://github.com/pipe-cd/pipecd/releases) to it. - Build your own container image based on `ghcr.io/pipe-cd/piped` image. ## Default environment values -You can use the envrionment values related to the deployment. +You can use the environment values related to the deployment. | Name | Description | Example | |-|-|-| diff --git a/docs/content/en/docs-v0.51.x/installation/install-control-plane/installing-controlplane-on-k8s.md b/docs/content/en/docs-v0.51.x/installation/install-control-plane/installing-controlplane-on-k8s.md index b41a8c71bd..64e7ad0709 100644 --- a/docs/content/en/docs-v0.51.x/installation/install-control-plane/installing-controlplane-on-k8s.md +++ b/docs/content/en/docs-v0.51.x/installation/install-control-plane/installing-controlplane-on-k8s.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.51.x/user-guide/managing-application/customizing-deployment/script-run.md b/docs/content/en/docs-v0.51.x/user-guide/managing-application/customizing-deployment/script-run.md index 69f0e20485..3c08c3dbf2 100644 --- a/docs/content/en/docs-v0.51.x/user-guide/managing-application/customizing-deployment/script-run.md +++ b/docs/content/en/docs-v0.51.x/user-guide/managing-application/customizing-deployment/script-run.md @@ -93,13 +93,13 @@ For example, If you are using the container platform and the offcial piped conta The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX commands available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). -If you want to use your commands, you can realize it with either step below. +If you want to use your commands, you can do that with either of the following steps. - Prepare your own environment container image then add [piped binary](https://github.com/pipe-cd/pipecd/releases) to it. - Build your own container image based on `ghcr.io/pipe-cd/piped` image. ## Default environment values -You can use the envrionment values related to the deployment. +You can use the environment values related to the deployment. | Name | Description | Example | |-|-|-| diff --git a/docs/content/en/docs-v0.52.x/installation/install-control-plane/installing-controlplane-on-k8s.md b/docs/content/en/docs-v0.52.x/installation/install-control-plane/installing-controlplane-on-k8s.md index b41a8c71bd..64e7ad0709 100644 --- a/docs/content/en/docs-v0.52.x/installation/install-control-plane/installing-controlplane-on-k8s.md +++ b/docs/content/en/docs-v0.52.x/installation/install-control-plane/installing-controlplane-on-k8s.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.52.x/user-guide/managing-application/customizing-deployment/script-run.md b/docs/content/en/docs-v0.52.x/user-guide/managing-application/customizing-deployment/script-run.md index 69f0e20485..3c08c3dbf2 100644 --- a/docs/content/en/docs-v0.52.x/user-guide/managing-application/customizing-deployment/script-run.md +++ b/docs/content/en/docs-v0.52.x/user-guide/managing-application/customizing-deployment/script-run.md @@ -93,13 +93,13 @@ For example, If you are using the container platform and the offcial piped conta The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX commands available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). -If you want to use your commands, you can realize it with either step below. +If you want to use your commands, you can do that with either of the following steps. - Prepare your own environment container image then add [piped binary](https://github.com/pipe-cd/pipecd/releases) to it. - Build your own container image based on `ghcr.io/pipe-cd/piped` image. ## Default environment values -You can use the envrionment values related to the deployment. +You can use the environment values related to the deployment. | Name | Description | Example | |-|-|-| diff --git a/docs/content/en/docs-v0.53.x/installation/install-control-plane/installing-controlplane-on-k8s.md b/docs/content/en/docs-v0.53.x/installation/install-control-plane/installing-controlplane-on-k8s.md index b41a8c71bd..64e7ad0709 100644 --- a/docs/content/en/docs-v0.53.x/installation/install-control-plane/installing-controlplane-on-k8s.md +++ b/docs/content/en/docs-v0.53.x/installation/install-control-plane/installing-controlplane-on-k8s.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.53.x/user-guide/managing-application/customizing-deployment/script-run.md b/docs/content/en/docs-v0.53.x/user-guide/managing-application/customizing-deployment/script-run.md index 69f0e20485..3c08c3dbf2 100644 --- a/docs/content/en/docs-v0.53.x/user-guide/managing-application/customizing-deployment/script-run.md +++ b/docs/content/en/docs-v0.53.x/user-guide/managing-application/customizing-deployment/script-run.md @@ -93,13 +93,13 @@ For example, If you are using the container platform and the offcial piped conta The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX commands available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). -If you want to use your commands, you can realize it with either step below. +If you want to use your commands, you can do that with either of the following steps. - Prepare your own environment container image then add [piped binary](https://github.com/pipe-cd/pipecd/releases) to it. - Build your own container image based on `ghcr.io/pipe-cd/piped` image. ## Default environment values -You can use the envrionment values related to the deployment. +You can use the environment values related to the deployment. | Name | Description | Example | |-|-|-| diff --git a/docs/content/en/docs-v0.54.x/installation/install-control-plane/installing-controlplane-on-k8s.md b/docs/content/en/docs-v0.54.x/installation/install-control-plane/installing-controlplane-on-k8s.md index b41a8c71bd..64e7ad0709 100644 --- a/docs/content/en/docs-v0.54.x/installation/install-control-plane/installing-controlplane-on-k8s.md +++ b/docs/content/en/docs-v0.54.x/installation/install-control-plane/installing-controlplane-on-k8s.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.54.x/user-guide/managing-application/customizing-deployment/script-run.md b/docs/content/en/docs-v0.54.x/user-guide/managing-application/customizing-deployment/script-run.md index 69f0e20485..3c08c3dbf2 100644 --- a/docs/content/en/docs-v0.54.x/user-guide/managing-application/customizing-deployment/script-run.md +++ b/docs/content/en/docs-v0.54.x/user-guide/managing-application/customizing-deployment/script-run.md @@ -93,13 +93,13 @@ For example, If you are using the container platform and the offcial piped conta The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX commands available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). -If you want to use your commands, you can realize it with either step below. +If you want to use your commands, you can do that with either of the following steps. - Prepare your own environment container image then add [piped binary](https://github.com/pipe-cd/pipecd/releases) to it. - Build your own container image based on `ghcr.io/pipe-cd/piped` image. ## Default environment values -You can use the envrionment values related to the deployment. +You can use the environment values related to the deployment. | Name | Description | Example | |-|-|-| diff --git a/docs/content/en/docs-v0.55.x/installation/install-control-plane/installing-controlplane-on-k8s.md b/docs/content/en/docs-v0.55.x/installation/install-control-plane/installing-controlplane-on-k8s.md index b41a8c71bd..64e7ad0709 100644 --- a/docs/content/en/docs-v0.55.x/installation/install-control-plane/installing-controlplane-on-k8s.md +++ b/docs/content/en/docs-v0.55.x/installation/install-control-plane/installing-controlplane-on-k8s.md @@ -62,7 +62,7 @@ spec: See [ConfigurationReference](../../../user-guide/managing-controlplane/configuration-reference/) for the full configuration. -After all, install the Control Plane as bellow: +After that, install the Control Plane as below: ``` console helm upgrade -i pipecd oci://ghcr.io/pipe-cd/chart/pipecd --version {{< blocks/latest_version >}} --namespace={NAMESPACE} \ diff --git a/docs/content/en/docs-v0.55.x/user-guide/managing-application/customizing-deployment/script-run.md b/docs/content/en/docs-v0.55.x/user-guide/managing-application/customizing-deployment/script-run.md index 69f0e20485..3c08c3dbf2 100644 --- a/docs/content/en/docs-v0.55.x/user-guide/managing-application/customizing-deployment/script-run.md +++ b/docs/content/en/docs-v0.55.x/user-guide/managing-application/customizing-deployment/script-run.md @@ -93,13 +93,13 @@ For example, If you are using the container platform and the offcial piped conta The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX commands available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). -If you want to use your commands, you can realize it with either step below. +If you want to use your commands, you can do that with either of the following steps. - Prepare your own environment container image then add [piped binary](https://github.com/pipe-cd/pipecd/releases) to it. - Build your own container image based on `ghcr.io/pipe-cd/piped` image. ## Default environment values -You can use the envrionment values related to the deployment. +You can use the environment values related to the deployment. | Name | Description | Example | |-|-|-| From 60361accc94be85eeafa6554169a0c8608739c38 Mon Sep 17 00:00:00 2001 From: e-esakman Date: Tue, 28 Apr 2026 22:50:39 +0530 Subject: [PATCH 2/3] fix typos Signed-off-by: e-esakman --- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../user-guide/managing-piped/adding-a-cloud-provider.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../user-guide/managing-piped/adding-a-cloud-provider.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../user-guide/managing-piped/adding-a-cloud-provider.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../user-guide/managing-piped/adding-a-cloud-provider.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../user-guide/managing-piped/adding-a-cloud-provider.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../managing-application/customizing-deployment/custom-sync.md | 2 +- .../user-guide/managing-piped/adding-a-cloud-provider.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../managing-application/customizing-deployment/custom-sync.md | 2 +- .../user-guide/managing-piped/adding-a-cloud-provider.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../managing-application/customizing-deployment/custom-sync.md | 2 +- .../user-guide/managing-piped/adding-a-cloud-provider.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../managing-application/customizing-deployment/custom-sync.md | 2 +- .../user-guide/managing-piped/adding-a-cloud-provider.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../managing-application/customizing-deployment/custom-sync.md | 2 +- .../user-guide/managing-piped/adding-a-cloud-provider.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../managing-application/customizing-deployment/custom-sync.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../managing-application/customizing-deployment/custom-sync.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../managing-application/customizing-deployment/custom-sync.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../managing-application/customizing-deployment/custom-sync.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../managing-application/customizing-deployment/custom-sync.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../managing-application/customizing-deployment/custom-sync.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- .../user-guide/managing-piped/adding-a-platform-provider.md | 2 +- 39 files changed, 39 insertions(+), 39 deletions(-) diff --git a/docs/content/en/docs-dev/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-dev/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-dev/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-dev/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.39.x/user-guide/managing-piped/adding-a-cloud-provider.md b/docs/content/en/docs-v0.39.x/user-guide/managing-piped/adding-a-cloud-provider.md index e05aad45af..b5435403b6 100644 --- a/docs/content/en/docs-v0.39.x/user-guide/managing-piped/adding-a-cloud-provider.md +++ b/docs/content/en/docs-v0.39.x/user-guide/managing-piped/adding-a-cloud-provider.md @@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.39.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.39.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.39.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.39.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.40.x/user-guide/managing-piped/adding-a-cloud-provider.md b/docs/content/en/docs-v0.40.x/user-guide/managing-piped/adding-a-cloud-provider.md index e05aad45af..b5435403b6 100644 --- a/docs/content/en/docs-v0.40.x/user-guide/managing-piped/adding-a-cloud-provider.md +++ b/docs/content/en/docs-v0.40.x/user-guide/managing-piped/adding-a-cloud-provider.md @@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.40.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.40.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.40.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.40.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.41.x/user-guide/managing-piped/adding-a-cloud-provider.md b/docs/content/en/docs-v0.41.x/user-guide/managing-piped/adding-a-cloud-provider.md index e05aad45af..b5435403b6 100644 --- a/docs/content/en/docs-v0.41.x/user-guide/managing-piped/adding-a-cloud-provider.md +++ b/docs/content/en/docs-v0.41.x/user-guide/managing-piped/adding-a-cloud-provider.md @@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.41.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.41.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.41.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.41.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.42.x/user-guide/managing-piped/adding-a-cloud-provider.md b/docs/content/en/docs-v0.42.x/user-guide/managing-piped/adding-a-cloud-provider.md index e05aad45af..b5435403b6 100644 --- a/docs/content/en/docs-v0.42.x/user-guide/managing-piped/adding-a-cloud-provider.md +++ b/docs/content/en/docs-v0.42.x/user-guide/managing-piped/adding-a-cloud-provider.md @@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.42.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.42.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.42.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.42.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.43.x/user-guide/managing-piped/adding-a-cloud-provider.md b/docs/content/en/docs-v0.43.x/user-guide/managing-piped/adding-a-cloud-provider.md index e05aad45af..b5435403b6 100644 --- a/docs/content/en/docs-v0.43.x/user-guide/managing-piped/adding-a-cloud-provider.md +++ b/docs/content/en/docs-v0.43.x/user-guide/managing-piped/adding-a-cloud-provider.md @@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.43.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.43.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.43.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.43.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.44.x/user-guide/managing-application/customizing-deployment/custom-sync.md b/docs/content/en/docs-v0.44.x/user-guide/managing-application/customizing-deployment/custom-sync.md index a18c9d22cd..c9201453d8 100644 --- a/docs/content/en/docs-v0.44.x/user-guide/managing-application/customizing-deployment/custom-sync.md +++ b/docs/content/en/docs-v0.44.x/user-guide/managing-application/customizing-deployment/custom-sync.md @@ -43,7 +43,7 @@ spec: Note: 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`. 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline. -3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first. +3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first. The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can: diff --git a/docs/content/en/docs-v0.44.x/user-guide/managing-piped/adding-a-cloud-provider.md b/docs/content/en/docs-v0.44.x/user-guide/managing-piped/adding-a-cloud-provider.md index e05aad45af..b5435403b6 100644 --- a/docs/content/en/docs-v0.44.x/user-guide/managing-piped/adding-a-cloud-provider.md +++ b/docs/content/en/docs-v0.44.x/user-guide/managing-piped/adding-a-cloud-provider.md @@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.44.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.44.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.44.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.44.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.45.x/user-guide/managing-application/customizing-deployment/custom-sync.md b/docs/content/en/docs-v0.45.x/user-guide/managing-application/customizing-deployment/custom-sync.md index a18c9d22cd..c9201453d8 100644 --- a/docs/content/en/docs-v0.45.x/user-guide/managing-application/customizing-deployment/custom-sync.md +++ b/docs/content/en/docs-v0.45.x/user-guide/managing-application/customizing-deployment/custom-sync.md @@ -43,7 +43,7 @@ spec: Note: 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`. 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline. -3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first. +3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first. The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can: diff --git a/docs/content/en/docs-v0.45.x/user-guide/managing-piped/adding-a-cloud-provider.md b/docs/content/en/docs-v0.45.x/user-guide/managing-piped/adding-a-cloud-provider.md index e05aad45af..b5435403b6 100644 --- a/docs/content/en/docs-v0.45.x/user-guide/managing-piped/adding-a-cloud-provider.md +++ b/docs/content/en/docs-v0.45.x/user-guide/managing-piped/adding-a-cloud-provider.md @@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.45.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.45.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.45.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.45.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.46.x/user-guide/managing-application/customizing-deployment/custom-sync.md b/docs/content/en/docs-v0.46.x/user-guide/managing-application/customizing-deployment/custom-sync.md index 47d7d7a534..c077b3753b 100644 --- a/docs/content/en/docs-v0.46.x/user-guide/managing-application/customizing-deployment/custom-sync.md +++ b/docs/content/en/docs-v0.46.x/user-guide/managing-application/customizing-deployment/custom-sync.md @@ -43,7 +43,7 @@ spec: Note: 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`. 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline. -3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first. +3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first. The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can: diff --git a/docs/content/en/docs-v0.46.x/user-guide/managing-piped/adding-a-cloud-provider.md b/docs/content/en/docs-v0.46.x/user-guide/managing-piped/adding-a-cloud-provider.md index e05aad45af..b5435403b6 100644 --- a/docs/content/en/docs-v0.46.x/user-guide/managing-piped/adding-a-cloud-provider.md +++ b/docs/content/en/docs-v0.46.x/user-guide/managing-piped/adding-a-cloud-provider.md @@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.46.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.46.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.46.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.46.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.47.x/user-guide/managing-application/customizing-deployment/custom-sync.md b/docs/content/en/docs-v0.47.x/user-guide/managing-application/customizing-deployment/custom-sync.md index 47d7d7a534..c077b3753b 100644 --- a/docs/content/en/docs-v0.47.x/user-guide/managing-application/customizing-deployment/custom-sync.md +++ b/docs/content/en/docs-v0.47.x/user-guide/managing-application/customizing-deployment/custom-sync.md @@ -43,7 +43,7 @@ spec: Note: 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`. 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline. -3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first. +3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first. The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can: diff --git a/docs/content/en/docs-v0.47.x/user-guide/managing-piped/adding-a-cloud-provider.md b/docs/content/en/docs-v0.47.x/user-guide/managing-piped/adding-a-cloud-provider.md index e05aad45af..b5435403b6 100644 --- a/docs/content/en/docs-v0.47.x/user-guide/managing-piped/adding-a-cloud-provider.md +++ b/docs/content/en/docs-v0.47.x/user-guide/managing-piped/adding-a-cloud-provider.md @@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.47.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.47.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.47.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.47.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.48.x/user-guide/managing-application/customizing-deployment/custom-sync.md b/docs/content/en/docs-v0.48.x/user-guide/managing-application/customizing-deployment/custom-sync.md index 47d7d7a534..c077b3753b 100644 --- a/docs/content/en/docs-v0.48.x/user-guide/managing-application/customizing-deployment/custom-sync.md +++ b/docs/content/en/docs-v0.48.x/user-guide/managing-application/customizing-deployment/custom-sync.md @@ -43,7 +43,7 @@ spec: Note: 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`. 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline. -3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first. +3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first. The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can: diff --git a/docs/content/en/docs-v0.48.x/user-guide/managing-piped/adding-a-cloud-provider.md b/docs/content/en/docs-v0.48.x/user-guide/managing-piped/adding-a-cloud-provider.md index e05aad45af..b5435403b6 100644 --- a/docs/content/en/docs-v0.48.x/user-guide/managing-piped/adding-a-cloud-provider.md +++ b/docs/content/en/docs-v0.48.x/user-guide/managing-piped/adding-a-cloud-provider.md @@ -102,7 +102,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#cloudproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.48.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.48.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.48.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.48.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.49.x/user-guide/managing-application/customizing-deployment/custom-sync.md b/docs/content/en/docs-v0.49.x/user-guide/managing-application/customizing-deployment/custom-sync.md index 47d7d7a534..c077b3753b 100644 --- a/docs/content/en/docs-v0.49.x/user-guide/managing-application/customizing-deployment/custom-sync.md +++ b/docs/content/en/docs-v0.49.x/user-guide/managing-application/customizing-deployment/custom-sync.md @@ -43,7 +43,7 @@ spec: Note: 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`. 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline. -3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first. +3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first. The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can: diff --git a/docs/content/en/docs-v0.49.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.49.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.49.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.49.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.50.x/user-guide/managing-application/customizing-deployment/custom-sync.md b/docs/content/en/docs-v0.50.x/user-guide/managing-application/customizing-deployment/custom-sync.md index 47d7d7a534..c077b3753b 100644 --- a/docs/content/en/docs-v0.50.x/user-guide/managing-application/customizing-deployment/custom-sync.md +++ b/docs/content/en/docs-v0.50.x/user-guide/managing-application/customizing-deployment/custom-sync.md @@ -43,7 +43,7 @@ spec: Note: 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`. 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline. -3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first. +3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first. The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can: diff --git a/docs/content/en/docs-v0.50.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.50.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.50.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.50.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.51.x/user-guide/managing-application/customizing-deployment/custom-sync.md b/docs/content/en/docs-v0.51.x/user-guide/managing-application/customizing-deployment/custom-sync.md index 47d7d7a534..c077b3753b 100644 --- a/docs/content/en/docs-v0.51.x/user-guide/managing-application/customizing-deployment/custom-sync.md +++ b/docs/content/en/docs-v0.51.x/user-guide/managing-application/customizing-deployment/custom-sync.md @@ -43,7 +43,7 @@ spec: Note: 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`. 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline. -3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first. +3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first. The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can: diff --git a/docs/content/en/docs-v0.51.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.51.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.51.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.51.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.52.x/user-guide/managing-application/customizing-deployment/custom-sync.md b/docs/content/en/docs-v0.52.x/user-guide/managing-application/customizing-deployment/custom-sync.md index 47d7d7a534..c077b3753b 100644 --- a/docs/content/en/docs-v0.52.x/user-guide/managing-application/customizing-deployment/custom-sync.md +++ b/docs/content/en/docs-v0.52.x/user-guide/managing-application/customizing-deployment/custom-sync.md @@ -43,7 +43,7 @@ spec: Note: 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`. 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline. -3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first. +3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first. The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can: diff --git a/docs/content/en/docs-v0.52.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.52.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.52.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.52.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.53.x/user-guide/managing-application/customizing-deployment/custom-sync.md b/docs/content/en/docs-v0.53.x/user-guide/managing-application/customizing-deployment/custom-sync.md index 47d7d7a534..c077b3753b 100644 --- a/docs/content/en/docs-v0.53.x/user-guide/managing-application/customizing-deployment/custom-sync.md +++ b/docs/content/en/docs-v0.53.x/user-guide/managing-application/customizing-deployment/custom-sync.md @@ -43,7 +43,7 @@ spec: Note: 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`. 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline. -3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first. +3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first. The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can: diff --git a/docs/content/en/docs-v0.53.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.53.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.53.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.53.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.54.x/user-guide/managing-application/customizing-deployment/custom-sync.md b/docs/content/en/docs-v0.54.x/user-guide/managing-application/customizing-deployment/custom-sync.md index 47d7d7a534..c077b3753b 100644 --- a/docs/content/en/docs-v0.54.x/user-guide/managing-application/customizing-deployment/custom-sync.md +++ b/docs/content/en/docs-v0.54.x/user-guide/managing-application/customizing-deployment/custom-sync.md @@ -43,7 +43,7 @@ spec: Note: 1. You can use `CUSTOM_SYNC` with any current supporting application kind, but keep `alwaysUsePipeline` true to not run the application kind's default `QUICK_SYNC`. 2. Only one `CUSTOM_SYNC` stage should be used in an application pipeline. -3. The commands run with the enviroment variable `PATH` that refers `~/.piped/tools` at first. +3. The commands run with the environment variable `PATH` that refers `~/.piped/tools` at first. The public piped image available in PipeCD main repo (ref: [Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/cmd/piped/Dockerfile)) is based on [alpine](https://hub.docker.com/_/alpine/) and only has a few UNIX command available (ref: [piped-base Dockerfile](https://github.com/pipe-cd/pipecd/blob/master/tool/piped-base/Dockerfile)). If you want to use your commands (`sam` in the above example), you can: diff --git a/docs/content/en/docs-v0.54.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.54.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.54.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.54.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. diff --git a/docs/content/en/docs-v0.55.x/user-guide/managing-piped/adding-a-platform-provider.md b/docs/content/en/docs-v0.55.x/user-guide/managing-piped/adding-a-platform-provider.md index d231c26e38..f1fb3f1b20 100644 --- a/docs/content/en/docs-v0.55.x/user-guide/managing-piped/adding-a-platform-provider.md +++ b/docs/content/en/docs-v0.55.x/user-guide/managing-piped/adding-a-platform-provider.md @@ -100,7 +100,7 @@ It attempts to retrieve credentials in the following order: 3. From the pod running in EKS cluster via STS (SecurityTokenService). 4. From the EC2 Instance Role. -Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources controll (list/read/write). +Therefore, you don't have to set credentialsFile if you use the environment variables or the EC2 Instance Role. Keep in mind the IAM role/user that you use with your Piped must possess the IAM policy permission for at least `Lambda.Function` and `Lambda.Alias` resources control (list/read/write). See [ConfigurationReference](../configuration-reference/#platformproviderlambdaconfig) for the full configuration. From c930f93d25c113c07e2e193031558701a8b04966 Mon Sep 17 00:00:00 2001 From: e-esakman Date: Tue, 28 Apr 2026 23:40:03 +0530 Subject: [PATCH 3/3] fix exmaple.com typo in helm tests Signed-off-by: e-esakman --- pkg/app/piped/platformprovider/kubernetes/helm_test.go | 6 +++--- pkg/app/pipedv1/plugin/kubernetes/provider/helm_test.go | 6 +++--- .../plugin/kubernetes_multicluster/provider/helm_test.go | 6 +++--- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/pkg/app/piped/platformprovider/kubernetes/helm_test.go b/pkg/app/piped/platformprovider/kubernetes/helm_test.go index a09b93f52f..6916a9d09f 100644 --- a/pkg/app/piped/platformprovider/kubernetes/helm_test.go +++ b/pkg/app/piped/platformprovider/kubernetes/helm_test.go @@ -126,19 +126,19 @@ func TestVerifyHelmValueFilePath(t *testing.T) { { name: "Values file locates allowed remote URL (http)", appDir: "testdata/testhelm/appconfdir", - valueFilePath: "http://exmaple.com/values.yaml", + valueFilePath: "http://example.com/values.yaml", wantErr: false, }, { name: "Values file locates allowed remote URL (https)", appDir: "testdata/testhelm/appconfdir", - valueFilePath: "https://exmaple.com/values.yaml", + valueFilePath: "https://example.com/values.yaml", wantErr: false, }, { name: "Values file locates disallowed remote URL (ftp)", appDir: "testdata/testhelm/appconfdir", - valueFilePath: "ftp://exmaple.com/values.yaml", + valueFilePath: "ftp://example.com/values.yaml", wantErr: true, }, { diff --git a/pkg/app/pipedv1/plugin/kubernetes/provider/helm_test.go b/pkg/app/pipedv1/plugin/kubernetes/provider/helm_test.go index 21a9b4ae7f..5c90bf0a92 100644 --- a/pkg/app/pipedv1/plugin/kubernetes/provider/helm_test.go +++ b/pkg/app/pipedv1/plugin/kubernetes/provider/helm_test.go @@ -132,19 +132,19 @@ func TestVerifyHelmValueFilePath(t *testing.T) { { name: "Values file locates allowed remote URL (http)", appDir: "testdata/testhelm/appconfdir", - valueFilePath: "http://exmaple.com/values.yaml", + valueFilePath: "http://example.com/values.yaml", wantErr: false, }, { name: "Values file locates allowed remote URL (https)", appDir: "testdata/testhelm/appconfdir", - valueFilePath: "https://exmaple.com/values.yaml", + valueFilePath: "https://example.com/values.yaml", wantErr: false, }, { name: "Values file locates disallowed remote URL (ftp)", appDir: "testdata/testhelm/appconfdir", - valueFilePath: "ftp://exmaple.com/values.yaml", + valueFilePath: "ftp://example.com/values.yaml", wantErr: true, }, { diff --git a/pkg/app/pipedv1/plugin/kubernetes_multicluster/provider/helm_test.go b/pkg/app/pipedv1/plugin/kubernetes_multicluster/provider/helm_test.go index f0731fbce2..852841bc57 100644 --- a/pkg/app/pipedv1/plugin/kubernetes_multicluster/provider/helm_test.go +++ b/pkg/app/pipedv1/plugin/kubernetes_multicluster/provider/helm_test.go @@ -132,19 +132,19 @@ func TestVerifyHelmValueFilePath(t *testing.T) { { name: "Values file locates allowed remote URL (http)", appDir: "testdata/testhelm/appconfdir", - valueFilePath: "http://exmaple.com/values.yaml", + valueFilePath: "http://example.com/values.yaml", wantErr: false, }, { name: "Values file locates allowed remote URL (https)", appDir: "testdata/testhelm/appconfdir", - valueFilePath: "https://exmaple.com/values.yaml", + valueFilePath: "https://example.com/values.yaml", wantErr: false, }, { name: "Values file locates disallowed remote URL (ftp)", appDir: "testdata/testhelm/appconfdir", - valueFilePath: "ftp://exmaple.com/values.yaml", + valueFilePath: "ftp://example.com/values.yaml", wantErr: true, }, {