-
Notifications
You must be signed in to change notification settings - Fork 427
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
Showing
1 changed file
with
28 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,28 @@ | ||
# Assignment Proposal | ||
|
||
## Title | ||
|
||
Github Actions workflow for deploying to an AWS Lambda function. | ||
|
||
## Names and KTH ID | ||
|
||
- Jacopo Maragna ([email protected]) | ||
- Íñigo Aréjula Aísa ([email protected]) | ||
|
||
## Deadline | ||
|
||
- Week 3 | ||
|
||
## Category | ||
|
||
- Demo | ||
|
||
## Description | ||
|
||
In this assignment, we are going to create a Github Actions workflow that will deploy a AWS Lambda function. The workflow will be triggered when a new commit is pushed to the repository. We are going to adopt a modular approach, so we will have different files that can be used in different projects. We are going to set up different workflows that will be conditionally triggered based on the success of the previous one. | ||
|
||
What we aim to demonstrate the possibility to vary the deployment setup with a few slight changes in the configuration files. | ||
|
||
**Relevance** | ||
|
||
Github actions is one of the most common services for CI/CD. In this case, we will use it to deploy a AWS Lambda function. This is a very interesting use case, as AWS Lambda is a very popular service for serverless computing. We are going to automate all the precess since the code is changed until the final deployment is done. |