From 67f716a6c53d497fcaef659ebeb1b5930274d733 Mon Sep 17 00:00:00 2001
From: chrissap543 <89662350+chrissap543@users.noreply.github.com>
Date: Sat, 31 Aug 2024 10:35:36 +0200
Subject: [PATCH] Week 5: Demo Proposal (#2380)

* Demo Proposal Week 5

* Update README.md
---
 .../demo/week5/sapinski-amano/README.md       | 25 +++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 contributions/demo/week5/sapinski-amano/README.md

diff --git a/contributions/demo/week5/sapinski-amano/README.md b/contributions/demo/week5/sapinski-amano/README.md
new file mode 100644
index 0000000000..ebe5841db9
--- /dev/null
+++ b/contributions/demo/week5/sapinski-amano/README.md
@@ -0,0 +1,25 @@
+# Assignment Proposal
+
+## Title
+
+Ensuring Terraform environment stability with Github Actions
+
+## Names and KTH ID
+  - Christopher Sapinski (sapinski@kth.se)
+  - Katsutoshi Amano (amano@kth.se)
+
+## Deadline
+
+- Week 5
+
+## Category
+
+- Demo
+
+## Description
+
+We will show how in a workflow, that when Terraform files are modified, we can then check the veracity of the changes. Once that has been verified, the merged pull request will update the environment. 
+
+**Relevance**
+
+Terraform is an infrastructure-as-code tool. When you make changes to the test environment by modifying Terraform files, it is good to make sure that the modifications do not break any standards. It can also make a log in the pull request of what has changed. For example, instead of spending time in the AWS dashboard changing configurations, Terraform can automatically update the instance.