Merge branch 'master' into make-actions-plan-preview-handle-timeout-o…

…ption

.github/workflows/stale.yaml

@@ -0,0 +1,23 @@
+name: 'Close stale issues and PRs'
+on:
+  schedule:
+    - cron: '0 0 * * *'
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v8
+        with:
+          # Issues
+          stale-issue-message: 'This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.'
+          close-issue-message: 'This issue was closed because it has been stalled for 7 days with no activity. Feel free to reopen if still applicable.'
+          days-before-issue-stale: 180
+          days-before-issue-close: 7
+          exempt-issue-labels: 'not-auto-close,kind/bug,good first issue'
+          # PRs
+          stale-pr-message: 'This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.'
+          close-pr-message: 'This PR was closed because it has been stalled for 7 days with no activity. Feel free to reopen if still applicable.'
+          days-before-pr-stale: 30
+          days-before-pr-close: 7
+          delete-branch: true

.golangci.yml

@@ -9,23 +9,23 @@ run:
 linters:
   disable-all: true
   enable:
-    - prealloc
+    - depguard
+    - exportloopref
+    - gocritic
+    - goimports
+    - gosimple
     - ineffassign
-    - goerr113
     - misspell
-    - errcheck
-    - gosimple
+    - prealloc
     - staticcheck
-    - gosec
-    - gocritic
-    - unparam
-    - deadcode
-    - unconvert
-    - typecheck
     - stylecheck
-    - exportloopref
-    - depguard
-    - goimports
+    - typecheck
+    - unconvert
+    - unparam
+    # TODO: Enable these linters
+    # - errcheck
+    # - goerr113
+    # - gosec
 
 issues:
   exclude-rules:
@@ -38,10 +38,15 @@ output:
 
 linters-settings:
   depguard:
-    list-type: blacklist
-    include-go-root: true
-    packages-with-error-message:
-      - sync/atomic: "Use go.uber.org/atomic instead of sync/atomic"
-      - io/ioutil: "Use corresponding 'os' or 'io' functions instead."
+    rules:
+      main:
+        deny:
+          - pkg: "sync/atomic"
+            desc: "Use go.uber.org/atomic instead of sync/atomic."
+          - pkg: "io/ioutil"
+            desc: "Use corresponding 'os' or 'io' functions instead."
+  gocritic:
+    disabled-checks:
+      - appendAssign
   goimports:
     local-prefixes: github.com/pipe-cd/pipecd

Makefile

@@ -149,7 +149,7 @@ run/site:
 
 .PHONY: lint/go
 lint/go: FIX ?= false
-lint/go: VERSION ?= sha256:78d1bbd01a9886a395dc8374218a6c0b7b67694e725dd76f0c8ac1de411b85e8 #v1.46.2
+lint/go: VERSION ?= sha256:fb70c9b2e6d0763141f057abcafde7f88d5e4bb3b5882d6b14bc79382f04481c #v1.55.2
 lint/go: FLAGS ?= --rm --platform linux/amd64 -e GOCACHE=/repo/.cache/go-build -e GOLANGCI_LINT_CACHE=/repo/.cache/golangci-lint -v ${PWD}:/repo -w /repo -it
 lint/go:
 ifeq ($(FIX),true)

README.md

@@ -102,12 +102,13 @@ You can find a list of publicly recognized users of the PipeCD in the [ADOPTERS.
 <a href="https://github.com/sivchari"><img src="https://avatars.githubusercontent.com/u/55221074?v=4" title="sivchari" width="80" height="80"></a>
 <a href="https://github.com/kevin-namba"><img src="https://avatars.githubusercontent.com/u/68955641?v=4" title="kevin-namba" width="80" height="80"></a>
 <a href="https://github.com/ffjlabo"><img src="https://avatars.githubusercontent.com/u/40124947?v=4" title="ffjlabo" width="80" height="80"></a>
-<a href="https://github.com/TaKO8Ki"><img src="https://avatars.githubusercontent.com/u/41065217?v=4" title="TaKO8Ki" width="80" height="80"></a>
 <a href="https://github.com/kurochan"><img src="https://avatars.githubusercontent.com/u/591247?v=4" title="kurochan" width="80" height="80"></a>
+<a href="https://github.com/TaKO8Ki"><img src="https://avatars.githubusercontent.com/u/41065217?v=4" title="TaKO8Ki" width="80" height="80"></a>
 <a href="https://github.com/chaspy"><img src="https://avatars.githubusercontent.com/u/10370988?v=4" title="chaspy" width="80" height="80"></a>
 <a href="https://github.com/gkuga"><img src="https://avatars.githubusercontent.com/u/33643470?v=4" title="gkuga" width="80" height="80"></a>
 <a href="https://github.com/hungran"><img src="https://avatars.githubusercontent.com/u/26101787?v=4" title="hungran" width="80" height="80"></a>
 <a href="https://github.com/TonkyH"><img src="https://avatars.githubusercontent.com/u/50762864?v=4" title="TonkyH" width="80" height="80"></a>
+<a href="https://github.com/karamaru-alpha"><img src="https://avatars.githubusercontent.com/u/38310693?v=4" title="karamaru-alpha" width="80" height="80"></a>
 <a href="https://github.com/golemiso"><img src="https://avatars.githubusercontent.com/u/3282656?v=4" title="golemiso" width="80" height="80"></a>
 <a href="https://github.com/tnqv"><img src="https://avatars.githubusercontent.com/u/23372024?v=4" title="tnqv" width="80" height="80"></a>
 <a href="https://github.com/khanhtc3010"><img src="https://avatars.githubusercontent.com/u/9603918?v=4" title="khanhtc3010" width="80" height="80"></a>
@@ -117,10 +118,11 @@ You can find a list of publicly recognized users of the PipeCD in the [ADOPTERS.
 <a href="https://github.com/anhpnv"><img src="https://avatars.githubusercontent.com/u/40441000?v=4" title="anhpnv" width="80" height="80"></a>
 <a href="https://github.com/seipan"><img src="https://avatars.githubusercontent.com/u/88176012?v=4" title="seipan" width="80" height="80"></a>
 <a href="https://github.com/p0tr3c"><img src="https://avatars.githubusercontent.com/u/12850042?v=4" title="p0tr3c" width="80" height="80"></a>
+<a href="https://github.com/seitarof"><img src="https://avatars.githubusercontent.com/u/51070449?v=4" title="seitarof" width="80" height="80"></a>
 <a href="https://github.com/gotyoooo"><img src="https://avatars.githubusercontent.com/u/6133219?v=4" title="gotyoooo" width="80" height="80"></a>
 <a href="https://github.com/ShotaKitazawa"><img src="https://avatars.githubusercontent.com/u/19530785?v=4" title="ShotaKitazawa" width="80" height="80"></a>
-<a href="https://github.com/karamaru-alpha"><img src="https://avatars.githubusercontent.com/u/38310693?v=4" title="karamaru-alpha" width="80" height="80"></a>
 <a href="https://github.com/tennashi"><img src="https://avatars.githubusercontent.com/u/10219626?v=4" title="tennashi" width="80" height="80"></a>
+<a href="https://github.com/ouchi2501"><img src="https://avatars.githubusercontent.com/u/11391317?v=4" title="ouchi2501" width="80" height="80"></a>
 <a href="https://github.com/Abirdcfly"><img src="https://avatars.githubusercontent.com/u/5100555?v=4" title="Abirdcfly" width="80" height="80"></a>
 <a href="https://github.com/benjx1990"><img src="https://avatars.githubusercontent.com/u/72671586?v=4" title="benjx1990" width="80" height="80"></a>
 <a href="https://github.com/ductnn"><img src="https://avatars.githubusercontent.com/u/22121217?v=4" title="ductnn" width="80" height="80"></a>
@@ -138,17 +140,18 @@ You can find a list of publicly recognized users of the PipeCD in the [ADOPTERS.
 <a href="https://github.com/RikiyaFujii"><img src="https://avatars.githubusercontent.com/u/23261497?v=4" title="RikiyaFujii" width="80" height="80"></a>
 <a href="https://github.com/SakataAtsuki"><img src="https://avatars.githubusercontent.com/u/58636635?v=4" title="SakataAtsuki" width="80" height="80"></a>
 <a href="https://github.com/butterv"><img src="https://avatars.githubusercontent.com/u/15773082?v=4" title="butterv" width="80" height="80"></a>
-<a href="https://github.com/seitarof"><img src="https://avatars.githubusercontent.com/u/51070449?v=4" title="seitarof" width="80" height="80"></a>
 <a href="https://github.com/mura-s"><img src="https://avatars.githubusercontent.com/u/4702673?v=4" title="mura-s" width="80" height="80"></a>
 <a href="https://github.com/Warashi"><img src="https://avatars.githubusercontent.com/u/3600530?v=4" title="Warashi" width="80" height="80"></a>
 <a href="https://github.com/Linutux"><img src="https://avatars.githubusercontent.com/u/435352?v=4" title="Linutux" width="80" height="80"></a>
 <a href="https://github.com/hosht"><img src="https://avatars.githubusercontent.com/u/3858627?v=4" title="hosht" width="80" height="80"></a>
 <a href="https://github.com/ww24"><img src="https://avatars.githubusercontent.com/u/695166?v=4" title="ww24" width="80" height="80"></a>
 <a href="https://github.com/tnir"><img src="https://avatars.githubusercontent.com/u/10229505?v=4" title="tnir" width="80" height="80"></a>
+<a href="https://github.com/t-kikuc"><img src="https://avatars.githubusercontent.com/u/97105818?v=4" title="t-kikuc" width="80" height="80"></a>
 <a href="https://github.com/yoiki"><img src="https://avatars.githubusercontent.com/u/39365493?v=4" title="yoiki" width="80" height="80"></a>
 <a href="https://github.com/JohnTitor"><img src="https://avatars.githubusercontent.com/u/25030997?v=4" title="JohnTitor" width="80" height="80"></a>
 <a href="https://github.com/mugioka"><img src="https://avatars.githubusercontent.com/u/62197019?v=4" title="mugioka" width="80" height="80"></a>
 <a href="https://github.com/nnnkkk7"><img src="https://avatars.githubusercontent.com/u/68233204?v=4" title="nnnkkk7" width="80" height="80"></a>
+<a href="https://github.com/naonao2323"><img src="https://avatars.githubusercontent.com/u/74669884?v=4" title="naonao2323" width="80" height="80"></a>
 <a href="https://github.com/tokku5552"><img src="https://avatars.githubusercontent.com/u/69064290?v=4" title="tokku5552" width="80" height="80"></a>
 
 #

docs/content/en/docs-dev/faq/_index.md

@@ -49,3 +49,15 @@ Yes, you can use PipeCD for both mesh (Istio, SMI) applications and non-mesh app
 ### 6. What should I do if I lost my Piped key?
 
 You can create a new Piped key. Go to the `Piped` tab at `Settings` page, and click the vertical ellipsis of the Piped that you would like to create the new Piped key. Don't forget deleting the old Key, too.
+
+### 7. What is the strong point if PipeCD is used only for Kubernetes?
+
+- Simple interface, easy to understand no extra CRD required
+- Easy to install, upgrade, and manage (both the ControlPlane and the agent Piped)
+- Not strict depend on any Kubernetes API, not being part of issues for your Kubernetes cluster versioning upgrade
+- Easy to interact with any CI; Plan preview feature gives you an early look at what will be changed in your cluster even before manifests update
+- Insights show metrics like lead time, deployment frequency, MTTR, and change failure rate to measure delivery performance
+
+### 8. Is it open source?
+
+Yes, PipeCD is fully open source project with APACHE LICENSE, VERSION 2.0!!

docs/content/en/docs-dev/overview/_index.md

@@ -8,7 +8,7 @@ description: >
 
 ![](/images/pipecd-explanation.png)
 <p style="text-align: center;">
-PipeCD - a Gitops style continuous delivery solution
+PipeCD - a GitOps style continuous delivery solution
 </p>
 
 ## What Is PipeCD?
@@ -19,6 +19,17 @@ PipeCD provides a unified continuous delivery solution for multiple application
 
 ## Why PipeCD?
 
+- Simple, unified and easy to use but powerful pipeline definition to construct your deployment
+- Same deployment interface to deploy applications of any platform, including Kubernetes, Terraform, GCP Cloud Run, AWS Lambda, AWS ECS
+- No CRD or applications' manifest changes are required; Only need a pipeline definition along with your application manifests
+- No deployment credentials are exposed or required outside the application cluster
+- Built-in deployment analysis as part of the deployment pipeline to measure impact based on metrics, logs, emitted requests
+- Easy to interact with any CI; The CI tests and builds artifacts, PipeCD takes the rest
+- Insights show metrics like lead time, deployment frequency, MTTR and change failure rate to measure delivery performance
+- Designed to manage thousands of cross-platform applications in multi-cloud for company scale but also work well for small projects
+
+## PipeCD's Characteristics in detail
+
 **Visibility**
 - Deployment pipeline UI shows clarify what is happening
 - Separate logs viewer for each individual deployment
@@ -50,7 +61,9 @@ PipeCD provides a unified continuous delivery solution for multiple application
 
 ## Where should I go next?
 
-For a good understanding of the PipeCD's components, see the [Concepts](../concepts) page.
+For a good understanding of the PipeCD's components.
+- [Concepts](../concepts): describes each components.
+- [FAQ](../faq): describes the difference between PipeCD and other tools.
 
 If you are an **operator** wanting to install and configure PipeCD for other developers.
 - [Quickstart](../quickstart/)

docs/content/en/docs-dev/user-guide/configuration-reference.md

@@ -445,15 +445,25 @@ One of `yamlField` or `regex` is required.
 | serviceDefinitionFile | string | The path ECS Service configuration file. Allow file in both `yaml` and `json` format. The default value is `service.json`. See [here](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service_definition_parameters.html) for parameters.| No |
 | taskDefinitionFile | string | The path to ECS TaskDefinition configuration file. Allow file in both `yaml` and `json` format. The default value is `taskdef.json`. See [here](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html) for parameters. | No |
 | targetGroups | [ECSTargetGroupInput](#ecstargetgroupinput) | The target groups configuration, will be used to routing traffic to created task sets. | Yes (if you want to perform progressive delivery) |
+| runStandaloneTask | bool | Run standalone tasks during deployments. About standalone task, see [here](https://docs.aws.amazon.com/AmazonECS/latest/userguide/ecs_run_task-v2.html). The default value is `true`. |
 
 ### ECSTargetGroupInput
 
 | Field | Type | Description | Required |
 |-|-|-|-|
-| primary | ECSTargetGroupObject | The PRIMARY target group, will be used to register the PRIMARY ECS task set. | Yes |
-| canary | ECSTargetGroupObject | The CANARY target group, will be used to register the CANARY ECS task set if exist. It's required to enable PipeCD to perform the multi-stage deployment. | No |
+| primary | [ECSTargetGroupObject](#ecstargetgroupobject) | The PRIMARY target group, will be used to register the PRIMARY ECS task set. | Yes |
+| canary | [ECSTargetGroupObject](#ecstargetgroupobject) | The CANARY target group, will be used to register the CANARY ECS task set if exist. It's required to enable PipeCD to perform the multi-stage deployment. | No |
 
-Note: You can get examples for those object from [here](../../examples/#ecs-applications).
+#### ECSTargetGroupObject
+
+| Field | Type | Description | Required |
+|-|-|-|-|
+| targetGroupArn | string | The name of the container (as it appears in a container definition) to　associate with the load balancer | Yes |
+| containerName | string | The full Amazon Resource Name (ARN) of the Elastic Load Balancing target group or groups associated with a service or task set. | Yes |
+| containerPort | int | The port on the container to associate with the load balancer. | Yes |
+| LoadBalancerName | string | The name of the load balancer to associate with the Amazon ECS service or task set. | No |
+
+Note: The available values are identical to those found in the aws-sdk-go-v2 Types.LoadBalancer. For more details, please refer to [this link](https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/ecs/types#LoadBalancer) .
 
 ## ECSQuickSync
 

docs/content/en/docs-v0.45.x/faq/_index.md

@@ -49,3 +49,15 @@ Yes, you can use PipeCD for both mesh (Istio, SMI) applications and non-mesh app
 ### 6. What should I do if I lost my Piped key?
 
 You can create a new Piped key. Go to the `Piped` tab at `Settings` page, and click the vertical ellipsis of the Piped that you would like to create the new Piped key. Don't forget deleting the old Key, too.
+
+### 7. What is the strong point if PipeCD is used only for Kubernetes?
+
+- Simple interface, easy to understand no extra CRD required
+- Easy to install, upgrade, and manage (both the ControlPlane and the agent Piped)
+- Not strict depend on any Kubernetes API, not being part of issues for your Kubernetes cluster versioning upgrade
+- Easy to interact with any CI; Plan preview feature gives you an early look at what will be changed in your cluster even before manifests update
+- Insights show metrics like lead time, deployment frequency, MTTR, and change failure rate to measure delivery performance
+
+### 8. Is it open source?
+
+Yes, PipeCD is fully open source project with APACHE LICENSE, VERSION 2.0!!

docs/content/en/docs-v0.45.x/overview/_index.md

@@ -8,7 +8,7 @@ description: >
 
 ![](/images/pipecd-explanation.png)
 <p style="text-align: center;">
-PipeCD - a Gitops style continuous delivery solution
+PipeCD - a GitOps style continuous delivery solution
 </p>
 
 ## What Is PipeCD?
@@ -19,6 +19,17 @@ PipeCD provides a unified continuous delivery solution for multiple application
 
 ## Why PipeCD?
 
+- Simple, unified and easy to use but powerful pipeline definition to construct your deployment
+- Same deployment interface to deploy applications of any platform, including Kubernetes, Terraform, GCP Cloud Run, AWS Lambda, AWS ECS
+- No CRD or applications' manifest changes are required; Only need a pipeline definition along with your application manifests
+- No deployment credentials are exposed or required outside the application cluster
+- Built-in deployment analysis as part of the deployment pipeline to measure impact based on metrics, logs, emitted requests
+- Easy to interact with any CI; The CI tests and builds artifacts, PipeCD takes the rest
+- Insights show metrics like lead time, deployment frequency, MTTR and change failure rate to measure delivery performance
+- Designed to manage thousands of cross-platform applications in multi-cloud for company scale but also work well for small projects
+
+## PipeCD's Characteristics in detail
+
 **Visibility**
 - Deployment pipeline UI shows clarify what is happening
 - Separate logs viewer for each individual deployment
@@ -50,7 +61,9 @@ PipeCD provides a unified continuous delivery solution for multiple application
 
 ## Where should I go next?
 
-For a good understanding of the PipeCD's components, see the [Concepts](../concepts) page.
+For a good understanding of the PipeCD's components.
+- [Concepts](../concepts): describes each components.
+- [FAQ](../faq): describes the difference between PipeCD and other tools.
 
 If you are an **operator** wanting to install and configure PipeCD for other developers.
 - [Quickstart](../quickstart/)