Update deployment configuration spec for Lambda application

docs/content/en/docs/examples/_index.md

@@ -61,5 +61,5 @@ https://github.com/pipe-cd/examples
 |-----------------------------------------------------------------------------|-------------|
 | [simple](https://github.com/pipe-cd/examples/tree/master/lambda/simple) | Quick sync by rolling out the new version and switching all traffic to it. |
 | [canary](https://github.com/pipe-cd/examples/tree/master/lambda/canary) | Deployment pipeline with canary strategy. |
-| [bluegreen](https://github.com/pipe-cd/examples/tree/master/lambda/bluegreen) | Deployment pipeline with bluegreen strategy. |
-
+| [analysis](https://github.com/pipe-cd/examples/tree/master/lambda/analysis) | Deployment pipeline that contains an analysis stage. |
+| [remote-git](https://github.com/pipe-cd/examples/tree/master/kubernetes/remote-git) | Deploy the lambda code sourced from another Git repository. |

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

@@ -324,17 +324,12 @@ spec:
 | Field | Type | Description | Required |
 |-|-|-|-|
 
-### CloudRunTrafficRoutingStageOptions
-
-| Field | Type | Description | Required |
-|-|-|-|-|
-
 ### LambdaCanaryRolloutStageOptions
 
 | Field | Type | Description | Required |
 |-|-|-|-|
 
-### LambdaTrafficRoutingStageOptions
+### LambdaPromoteStageOptions
 
 | Field | Type | Description | Required |
 |-|-|-|-|

docs/content/en/docs/user-guide/examples.md

@@ -60,5 +60,6 @@ https://github.com/pipe-cd/examples
 |-----------------------------------------------------------------------------|-------------|
 | [simple](https://github.com/pipe-cd/examples/tree/master/lambda/simple) | Quick sync by rolling out the new version and switching all traffic to it. |
 | [canary](https://github.com/pipe-cd/examples/tree/master/lambda/canary) | Deployment pipeline with canary strategy. |
-| [bluegreen](https://github.com/pipe-cd/examples/tree/master/lambda/bluegreen) | Deployment pipeline with bluegreen strategy. |
+| [analysis](https://github.com/pipe-cd/examples/tree/master/lambda/analysis) | Deployment pipeline that contains an analysis stage. |
+| [remote-git](https://github.com/pipe-cd/examples/tree/master/kubernetes/remote-git) | Deploy the lambda code sourced from another Git repository. |
 

examples/README.remote.md

@@ -49,5 +49,5 @@ A repository contains some examples for PipeCD.
 |-----------------------------------------------------------------------------|-------------|
 | [simple](https://github.com/pipe-cd/examples/tree/master/lambda/simple) | Quick sync by rolling out the new version and switching all traffic to it. |
 | [canary](https://github.com/pipe-cd/examples/tree/master/lambda/canary) | Deployment pipeline with canary strategy. |
-| [bluegreen](https://github.com/pipe-cd/examples/tree/master/lambda/bluegreen) | Deployment pipeline with bluegreen strategy. |
-
+| [analysis](https://github.com/pipe-cd/examples/tree/master/lambda/analysis) | Deployment pipeline that contains an analysis stage. |
+| [remote-git](https://github.com/pipe-cd/examples/tree/master/kubernetes/remote-git) | Deploy the lambda code sourced from another Git repository. |

examples/lambda/bluegreen/.pipe.yaml → examples/lambda/analysis/.pipe.yaml

@@ -5,22 +5,22 @@ apiVersion: pipecd.dev/v1beta1
 kind: LambdaApp
 spec:
   input:
-    # Where to fetch the source code to create lambda package.
-    git: git@github.com:org/source-repo.git
-    path: lambdas/demoapp
-    ref: v1.0.0
+    # Lambda code sourced from the same Git repository.
+    path: lambdas/helloworld
   pipeline:
     stages:
       # Deploy workloads of the new version.
       # But this is still receiving no traffic.
       - name: LAMBDA_CANARY_ROLLOUT
-      # Change the traffic routing state where
-      # the new version will receive 100% of the traffic as soon as possible.
-      # This is known as blue-green strategy.
-      - name: LAMBDA_TRAFFIC_ROUTING
+      # Promote new version to receive amount of traffic.
+      - name: LAMBDA_PROMOTE
         with:
-          canary: 100
+          percent: 10
       # Optional: We can also add an ANALYSIS stage to verify the new version.
       # If this stage finds any not good metrics of the new version,
       # a rollback process to the previous version will be executed.
       - name: ANALYSIS
+      # Promote new version to receive all traffic.
+      - name: LAMBDA_PROMOTE
+        with:
+          percent: 100

examples/lambda/canary/.pipe.yaml

@@ -5,27 +5,21 @@ apiVersion: pipecd.dev/v1beta1
 kind: LambdaApp
 spec:
   input:
-    # Where to fetch the source code to create lambda package.
-    git: git@github.com:org/source-repo.git
-    path: lambdas/demoapp
-    ref: v1.0.0
+    # Lambda code sourced from the same Git repository.
+    path: lambdas/helloworld
   pipeline:
     stages:
       # Deploy workloads of the new version.
       # But this is still receiving no traffic.
       - name: LAMBDA_CANARY_ROLLOUT
-      # Change the traffic routing state where
-      # the new version will receive the specified percentage of traffic.
-      # This is known as multi-phase canary strategy.
-      - name: LAMBDA_TRAFFIC_ROUTING
+      # Promote new version to receive amount of traffic.
+      - name: LAMBDA_PROMOTE
         with:
-          canary: 10
-      # Optional: We can also add an ANALYSIS stage to verify the new version.
-      # If this stage finds any not good metrics of the new version,
-      # a rollback process to the previous version will be executed.
-      - name: ANALYSIS
-      # Change the traffic routing state where
-      # thre new version will receive 100% of the traffic.
-      - name: LAMBDA_TRAFFIC_ROUTING
+          percent: 10
+      - name: LAMBDA_PROMOTE
         with:
-          canary: 100
+          percent: 50
+      # Promote new version to receive all traffic.
+      - name: LAMBDA_PROMOTE
+        with:
+          percent: 100

examples/lambda/remote-git/.pipe.yaml

@@ -0,0 +1,10 @@
+# Quick sync by rolling out the new version and switching all traffic to it.
+# https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html
+apiVersion: pipecd.dev/v1beta1
+kind: LambdaApp
+spec:
+  input:
+    # Lambda code sourced from another Git repository.
+    git: git@github.com:org/source-repo.git
+    path: lambdas/helloworld
+    ref: v1.0.0

examples/lambda/simple/.pipe.yaml

@@ -4,8 +4,5 @@ apiVersion: pipecd.dev/v1beta1
 kind: LambdaApp
 spec:
   input:
-    # Where to fetch the source code to create lambda package.
-    # If the source code is inside the same repository "git" and "ref" can be omitted.
-    git: git@github.com:org/source-repo.git
-    path: lambdas/demoapp
-    ref: v1.0.0
+    # Lambda code sourced from the same Git repository.
+    path: lambdas/helloworld

pkg/config/deployment.go

@@ -67,9 +67,9 @@ type PipelineStage struct {
 	CloudRunSyncStageOptions    *CloudRunSyncStageOptions
 	CloudRunPromoteStageOptions *CloudRunPromoteStageOptions
 
-	LambdaSyncStageOptions           *LambdaSyncStageOptions
-	LambdaCanaryRolloutStageOptions  *LambdaCanaryRolloutStageOptions
-	LambdaTrafficRoutingStageOptions *LambdaTrafficRoutingStageOptions
+	LambdaSyncStageOptions          *LambdaSyncStageOptions
+	LambdaCanaryRolloutStageOptions *LambdaCanaryRolloutStageOptions
+	LambdaPromoteStageOptions       *LambdaPromoteStageOptions
 }
 
 type genericPipelineStage struct {
@@ -175,10 +175,10 @@ func (s *PipelineStage) UnmarshalJSON(data []byte) error {
 		if len(gs.With) > 0 {
 			err = json.Unmarshal(gs.With, s.LambdaCanaryRolloutStageOptions)
 		}
-	case model.StageLambdaTrafficRouting:
-		s.LambdaTrafficRoutingStageOptions = &LambdaTrafficRoutingStageOptions{}
+	case model.StageLambdaPromote:
+		s.LambdaPromoteStageOptions = &LambdaPromoteStageOptions{}
 		if len(gs.With) > 0 {
-			err = json.Unmarshal(gs.With, s.LambdaTrafficRoutingStageOptions)
+			err = json.Unmarshal(gs.With, s.LambdaPromoteStageOptions)
 		}
 
 	default:

pkg/config/deployment_lambda.go

@@ -52,29 +52,11 @@ type LambdaDeploymentInput struct {
 type LambdaSyncStageOptions struct {
 }
 
-// LambdaCanaryRolloutStageOptions contains all configurable values for a CLOUDRUN_PROMOTE stage.
+// LambdaCanaryRolloutStageOptions contains all configurable values for a CLOUDRUN_CANARY_ROLLOUT stage.
 type LambdaCanaryRolloutStageOptions struct {
 }
 
-// LambdaTrafficRoutingStageOptions contains all configurable values for a CLOUDRUN_TRAFFIC_ROUTING stage.
-type LambdaTrafficRoutingStageOptions struct {
-	// Which variant should receive all traffic.
-	// This can be either "primary" or "canary".
-	All string `json:"all"`
-	// The percentage of traffic should be routed to PRIMARY variant.
-	Primary int `json:"primary"`
-	// The percentage of traffic should be routed to CANARY variant.
-	Canary int `json:"canary"`
-}
-
-func (opts LambdaTrafficRoutingStageOptions) Percentages() (primary, canary int) {
-	switch opts.All {
-	case "primary":
-		primary = 100
-		return
-	case "canary":
-		canary = 100
-		return
-	}
-	return opts.Primary, opts.Canary
+// LambdaPromoteStageOptions contains all configurable values for a CLOUDRUN_PROMOTE stage.
+type LambdaPromoteStageOptions struct {
+	Percent int `json:"percent"`
 }

pkg/config/testdata/application/cloudrun-app-bluegreen.yaml

@@ -12,7 +12,7 @@ spec:
       # Change the traffic routing state where
       # the new version will receive 100% of the traffic as soon as possible.
       # This is known as blue-green strategy.
-      - name: CLOUDRUN_TRAFFIC_ROUTING
+      - name: CLOUDRUN_PROMOTE
         with:
           canary: 100
       # Optional: We can also add an ANALYSIS stage to verify the new version.

pkg/config/testdata/application/cloudrun-app-canary.yaml

@@ -12,7 +12,7 @@ spec:
       # Change the traffic routing state where
       # the new version will receive the specified percentage of traffic.
       # This is known as multi-phase canary strategy.
-      - name: CLOUDRUN_TRAFFIC_ROUTING
+      - name: CLOUDRUN_PROMOTE
         with:
           canary: 10
       # Optional: We can also add an ANALYSIS stage to verify the new version.
@@ -21,6 +21,6 @@ spec:
       - name: ANALYSIS
       # Change the traffic routing state where
       # thre new version will receive 100% of the traffic.
-      - name: CLOUDRUN_TRAFFIC_ROUTING
+      - name: CLOUDRUN_PROMOTE
         with:
           canary: 100

pkg/config/testdata/application/lambda-app-bluegreen.yaml

@@ -16,7 +16,7 @@ spec:
       # Change the traffic routing state where
       # the new version will receive 100% of the traffic as soon as possible.
       # This is known as blue-green strategy.
-      - name: LAMBDA_TRAFFIC_ROUTING
+      - name: LAMBDA_PROMOTE
         with:
           canary: 100
       # Optional: We can also add an ANALYSIS stage to verify the new version.

pkg/config/testdata/application/lambda-app-canary.yaml

@@ -16,7 +16,7 @@ spec:
       # Change the traffic routing state where
       # the new version will receive the specified percentage of traffic.
       # This is known as multi-phase canary strategy.
-      - name: LAMBDA_TRAFFIC_ROUTING
+      - name: LAMBDA_PROMOTE
         with:
           canary: 10
       # Optional: We can also add an ANALYSIS stage to verify the new version.
@@ -25,6 +25,6 @@ spec:
       - name: ANALYSIS
       # Change the traffic routing state where
       # thre new version will receive 100% of the traffic.
-      - name: LAMBDA_TRAFFIC_ROUTING
+      - name: LAMBDA_PROMOTE
         with:
           canary: 100

pkg/model/stage.go

@@ -71,9 +71,8 @@ const (
 	// StageLambdaCanaryRollout represents the state where
 	// the workloads of the new version has been rolled out.
 	StageLambdaCanaryRollout Stage = "LAMBDA_CANARY_ROLLOUT"
-	// StageLambdaTrafficRouting represents the state where the traffic to application
-	// should be splitted as the specified percentage to previous version and new version.
-	StageLambdaTrafficRouting Stage = "LAMBDA_TRAFFIC_ROUTING"
+	// StageLambdaPromote prmotes the new version to receive amount of traffic.
+	StageLambdaPromote Stage = "LAMBDA_PROMOTE"
 
 	// StageRollback represents a state where
 	// the all temporarily created stages will be reverted to