remove only tls1.1

[7hunderbird]

I first experimented with the version of CloudFront's terraform module in PR #42, then changed it to try taking away the TLS v1.1 option in the origin resource.

This PR looks to see what is different in the state of the GitHub Actions state when I change only the TLS 1.1.

I'm curious about both how Overmind itself handles the "state" of the system, as well as understanding how GitHub Actions affects the results of Overmind. I would expect that there isn't shared state between each build on GitHub Actions, and this would help me validate that assumption.

[github-actions]

Expected Changes

cloudfront-distribution › E15V1JM5GZXBKB

--- current
+++ planned
@@ -95,22 +95,21 @@
       custom_header: []
       custom_origin_config: []
       domain_name: s3-one-apt-catfish.s3.eu-west-2.amazonaws.com
-      origin_access_control_id: ""
-      origin_id: s3_one
+      origin_access_control_id: E23BFWHZQZKBPZ
+      origin_id: s3_oac
       origin_path: ""
       origin_shield: []
-      s3_origin_config:
-        - origin_access_identity: origin-access-identity/cloudfront/E2X23HICB2NVF3
+      s3_origin_config: []
     - connection_attempts: 3
       connection_timeout: 10
       custom_header: []
       custom_origin_config: []
       domain_name: s3-one-apt-catfish.s3.eu-west-2.amazonaws.com
-      origin_access_control_id: E23BFWHZQZKBPZ
-      origin_id: s3_oac
+      origin_id: s3_one
       origin_path: ""
       origin_shield: []
-      s3_origin_config: []
+      s3_origin_config:
+        - origin_access_identity: origin-access-identity/cloudfront/E2X23HICB2NVF3
     - connection_attempts: 3
       connection_timeout: 10
       custom_header:
@@ -126,7 +116,6 @@
           origin_read_timeout: 30
           origin_ssl_protocols:
             - TLSv1
-            - TLSv1.1
             - TLSv1.2
       domain_name: appsync.terraform-aws-modules.modules.tf
       origin_access_control_id: ""

Blast Radius

Items	Edges
113	108

Open in Overmind