Skip to content

Commit 76e0f8e

Browse files
authored
Week 3: demo proposal (#2373)
1 parent 0e623cc commit 76e0f8e

File tree

1 file changed

+28
-0
lines changed
  • contributions/demo/week3/jmaragna-inigoaa

1 file changed

+28
-0
lines changed
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# Assignment Proposal
2+
3+
## Title
4+
5+
Github Actions workflow for deploying to an AWS Lambda function.
6+
7+
## Names and KTH ID
8+
9+
- Jacopo Maragna ([email protected])
10+
- Íñigo Aréjula Aísa ([email protected])
11+
12+
## Deadline
13+
14+
- Week 3
15+
16+
## Category
17+
18+
- Demo
19+
20+
## Description
21+
22+
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.
23+
24+
What we aim to demonstrate the possibility to vary the deployment setup with a few slight changes in the configuration files.
25+
26+
**Relevance**
27+
28+
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.

0 commit comments

Comments
 (0)