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.

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

Week 3: demo proposal #2373

Merged
merged 1 commit into from
Sep 3, 2024
Merged
Changes from all commits
Commits
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
28 changes: 28 additions & 0 deletions contributions/demo/week3/jmaragna-inigoaa/README.md
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.
Loading