Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Week 5: Demo Proposal #2380

Merged
merged 2 commits into from
Aug 31, 2024
Merged

Week 5: Demo Proposal #2380

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8e0f261
Demo Proposal Week 5
chrissap543 Aug 29, 2024
8a21f99
Update README.md
chrissap543 Aug 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions contributions/demo/week5/sapinski-amano/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Assignment Proposal

## Title

Ensuring Terraform environment stability with Github Actions

## Names and KTH ID
- Christopher Sapinski ([email protected])
- Katsutoshi Amano ([email protected])

## 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.
Loading