From cb8b144690f29ceb026a43e5c19a373bb53384b9 Mon Sep 17 00:00:00 2001
From: caiocsgomes <caiocsgomes@gmail.com>
Date: Sat, 30 Dec 2023 18:16:36 +0200
Subject: [PATCH 1/2] adding http to http redirection to cloudfront default
 behaviour

---
 infra/cloudfront.tf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/infra/cloudfront.tf b/infra/cloudfront.tf
index f0f3170..57647d1 100644
--- a/infra/cloudfront.tf
+++ b/infra/cloudfront.tf
@@ -53,7 +53,7 @@ resource "aws_cloudfront_distribution" "s3_distribution" {
       }
     }
 
-    viewer_protocol_policy = "allow-all"
+    viewer_protocol_policy = "redirect-to-https"
     min_ttl                = 0
     default_ttl            = 3600
     max_ttl                = 86400

From b576053aef8acad116b5fef9f3ba8396e184b574 Mon Sep 17 00:00:00 2001
From: caiocsgomes <caiocsgomes@gmail.com>
Date: Sat, 30 Dec 2023 19:11:37 +0200
Subject: [PATCH 2/2] removing old files and testing pipeline

---
 app/content/posts/gha-notes/index.md | 40 ----------------------------
 1 file changed, 40 deletions(-)
 delete mode 100644 app/content/posts/gha-notes/index.md

diff --git a/app/content/posts/gha-notes/index.md b/app/content/posts/gha-notes/index.md
deleted file mode 100644
index 75c5545..0000000
--- a/app/content/posts/gha-notes/index.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: "The basics of Github Actions"
-date: 2030-01-22T22:00:00-03:00
-slug: gha-notes
-category: github-actions
-description: "A summary of Github Actions"
-draft: false
----
-
-# Notes about Github Actions
-
-This is a summary about the main features of Github Actions and a way to speep up its use when necessary. I'll go over the features, with examples, that are most used in any pipeline and provide links to the documentation if a deep dive is necessary. This will probably be enough for most pipelines.
-
-## GitHub Actions
-
-[**GitHub actions**](https://docs.github.com/en/actions/quickstart) is an automation service that allows us to automate all kinds of repository related processes and actions. Using GitHub Actions we provide GitHub with a *yml* file describing our *workflow* in *steps*, and it will run the workflow based on an *event* that can be a *push*. This way everytime we make a push to the repository it will run the actions described in the yml file with our repository. This is perfect to build **CI/CD** pipelines.
-
-## Basic components
-### Workflows
-### Jobs
-### Steps
-### Actions
-### Runner
-
-## Events
-### Filters
-### Activity types
-
-## Context objects
-
-## Uploading and downloading artifacts
-
-## Caching
-
-## Environmental variables
-
-## Secrets
-
-## Conditional workflows
-