-
Notifications
You must be signed in to change notification settings - Fork 428
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
b5e4652
commit 8e0f261
Showing
1 changed file
with
25 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Demo 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. |