Heitor Lessa
Heitor Lessa
Currently, all of our CVE notifications are related to JS/TS dependencies we often don't control. This issue is to track the rewrite of our Perf-test that uses CDK to deploy...
Booking is currently written in Python, and needs unit testing for the following functions: * [ ] cancel-booking * [ ] confirm-booking * [ ] notify-booking * [ ] reserve-booking...
As per discussion on #87, there's value in bringing Payment into GraphQL Schema and possibly integrate with Stripe directly via HTTP data source. We'd also need custom mutations and fine-grained...
Currently, `process_booking` mutation in AppSync currently triggers a Step Functions async, and `reserve-booking` Lambda function is the first called to create a booking reservation. Idea here is to improve front-end...
We need to make it easier to delete entire stack and update services individually from local workstation. After exporting amplify-managed resources to Parameter Store, we could manipulate them locally to...
QLDB is now GA and we could experiment as a replacement for DynamoDB.
Currently, flights within booking are done through `@connection` (GSI). As we work to implement a cleanup strategy to keep costs down for customers, we could clean up flights DB more...
This should be closed once it's clear how to deploy back-end only from a developer's laptop (no CI involved). ## TODO * Create `dev` target in `Makefile`: `make dev` *...
Currently, Step Functions is triggered via `process_booking` mutation in AppSync. AppSync resolver creates the following payload that is used as an input for Step Functions: ```json { "outboundFlightId": "1688a4f6-69dd-4590-833e-f349384df465", "customerId":...
Add following identifier to resources that support tags: * [ ] `Environment: Demo` * [ ] `Solution: github.com/aws-samples/aws-serverless-airline-booking` * anything else that could be helpful