v1.2.5

API Gateway + Catalog Lambda

This one was bigger than expected because I missed some pieces along the way.

1. I forgot to build a catalog function that returns the current list
2. My understanding of gateways was a little bit off

• Responses are normalized so I made sure my responses are consistent
• I thought I needed an openapi spec but that was wrong too

So now we've got 3 total lambdas along with consistent responses from all of em. We've also got a quantity counter on each of our product listings. Might've cut corners on this one a little bit when it comes to the site but glad everything came out alright.

Its actually in a usable state, only thing left would be payment processing and you could....technically go live.

Other Changes

• Since there's a chance our gateway's id can change in between runs, I made a job output for it.
  • Check #ac0ab6329fa78b3d623c56089837bf76fec73063
• Added a catalog lambda to return a list of products available
  • Light oversight. Yeah we need to be able to interact with the store but unless I passed DB credentials to the site, I'll never know the current state
• Updated Lambda packages and web client's method calls
  • There were some quirks that I've mentioned above

Screenies

Successful sale thru gateway

Site, lambdas, gateway, and RDS are LIVE

What's Changed

• 29 API Gateway & Tying it all together by @Guysnacho in #17
• Fix cli env update potentially maybe by @Guysnacho in #18

Full Changelog: v1.2.4...v1.2.5