Regen tests after rebasing

klothoplatform · Feb 1, 2024 · 07b9c19 · 07b9c19
1 parent 4c8d483
commit 07b9c19
Show file tree

Hide file tree

Showing 4 changed files with 27 additions and 27 deletions.
diff --git a/pkg/engine2/testdata/ecs_rds.expect.yaml b/pkg/engine2/testdata/ecs_rds.expect.yaml
@@ -182,6 +182,11 @@ resources:
               Protocol: "-1"
               ToPort: 0
         IngressRules:
+            - Description: Allow ingress traffic from within the same security group
+              FromPort: 0
+              Protocol: "-1"
+              Self: true
+              ToPort: 0
             - CidrBlocks:
                 - 10.0.128.0/18
               Description: Allow ingress traffic from ip addresses within the subnet subnet-0
@@ -194,11 +199,6 @@ resources:
               FromPort: 0
               Protocol: "-1"
               ToPort: 0
-            - Description: Allow ingress traffic from within the same security group
-              FromPort: 0
-              Protocol: "-1"
-              Self: true
-              ToPort: 0
         Vpc: aws:vpc:vpc-0
     aws:route_table:vpc-0:subnet-0-route_table:
         Routes:

diff --git a/pkg/engine2/testdata/k8s_api.expect.yaml b/pkg/engine2/testdata/k8s_api.expect.yaml
@@ -267,12 +267,12 @@ resources:
                         - ec2.amazonaws.com
             Version: "2012-10-17"
         ManagedPolicies:
+            - arn:aws:iam::aws:policy/CloudWatchAgentServerPolicy
+            - arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore
             - arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy
             - arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly
             - arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy
             - arn:aws:iam::aws:policy/AWSCloudMapFullAccess
-            - arn:aws:iam::aws:policy/CloudWatchAgentServerPolicy
-            - arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore
     aws:iam_role:pod2:
         AssumeRolePolicyDoc:
             Statement:
@@ -484,12 +484,6 @@ resources:
               Protocol: "-1"
               ToPort: 0
         IngressRules:
-            - CidrBlocks:
-                - 0.0.0.0/0
-              Description: Allows ingress traffic from the EKS control plane
-              FromPort: 9443
-              Protocol: TCP
-              ToPort: 9443
             - Description: Allow ingress traffic from within the same security group
               FromPort: 0
               Protocol: "-1"
@@ -507,6 +501,12 @@ resources:
               FromPort: 0
               Protocol: "-1"
               ToPort: 0
+            - CidrBlocks:
+                - 0.0.0.0/0
+              Description: Allows ingress traffic from the EKS control plane
+              FromPort: 9443
+              Protocol: TCP
+              ToPort: 9443
         Vpc: aws:vpc:vpc-0
     aws:route_table:vpc-0:subnet-0-route_table:
         Routes:

diff --git a/pkg/engine2/testdata/remove_path.expect.yaml b/pkg/engine2/testdata/remove_path.expect.yaml
@@ -215,12 +215,6 @@ resources:
               Protocol: "-1"
               ToPort: 0
         IngressRules:
-            - CidrBlocks:
-                - 10.0.192.0/18
-              Description: Allow ingress traffic from ip addresses within the subnet subnet-1
-              FromPort: 0
-              Protocol: "-1"
-              ToPort: 0
             - Description: Allow ingress traffic from within the same security group
               FromPort: 0
               Protocol: "-1"
@@ -232,6 +226,12 @@ resources:
               FromPort: 0
               Protocol: "-1"
               ToPort: 0
+            - CidrBlocks:
+                - 10.0.192.0/18
+              Description: Allow ingress traffic from ip addresses within the subnet subnet-1
+              FromPort: 0
+              Protocol: "-1"
+              ToPort: 0
         Vpc: aws:vpc:vpc-0
     aws:route_table:vpc-0:subnet-0-route_table:
         Routes:

diff --git a/pkg/engine2/testdata/vpc_import_to_lambda.err.json b/pkg/engine2/testdata/vpc_import_to_lambda.err.json
@@ -68,45 +68,45 @@
   {
     "error": {
       "chain": [
-        "required property Id is not set on resource aws:subnet:subnet2"
+        "required property Id is not set on resource aws:subnet:subnet3"
       ]
     },
     "error_code": "config_invalid",
     "property": "Id",
-    "resource": "aws:subnet:subnet2",
+    "resource": "aws:subnet:subnet3",
     "value": null
   },
   {
     "error": {
       "chain": [
-        "required property Id is not set on resource aws:subnet:subnet3"
+        "required property Id is not set on resource aws:subnet:subnet4"
       ]
     },
     "error_code": "config_invalid",
     "property": "Id",
-    "resource": "aws:subnet:subnet3",
+    "resource": "aws:subnet:subnet4",
     "value": null
   },
   {
     "error": {
       "chain": [
-        "required property Id is not set on resource aws:subnet:subnet4"
+        "required property Id is not set on resource aws:subnet:vpc:subnet1"
       ]
     },
     "error_code": "config_invalid",
     "property": "Id",
-    "resource": "aws:subnet:subnet4",
+    "resource": "aws:subnet:vpc:subnet1",
     "value": null
   },
   {
     "error": {
       "chain": [
-        "required property Id is not set on resource aws:subnet:vpc:subnet1"
+        "required property Id is not set on resource aws:subnet:vpc:subnet2"
       ]
     },
     "error_code": "config_invalid",
     "property": "Id",
-    "resource": "aws:subnet:vpc:subnet1",
+    "resource": "aws:subnet:vpc:subnet2",
     "value": null
   },
   {