This is after we get some of the lambda workflow set up after ~stealing~ borrowing some of Graduate's aws credits.
Basically, the lambda handlers are where the business logic will be stored with recording statistics like whether a pair has met or not. I'm not exactly sure what the parameters would be when the request url is hit from the user/slack bot side, so you might wanna look into that. I suspect we have an event type enum with some sort of data passed into the payload?
This is after we get some of the lambda workflow set up after ~stealing~ borrowing some of Graduate's aws credits.
Basically, the lambda handlers are where the business logic will be stored with recording statistics like whether a pair has met or not. I'm not exactly sure what the parameters would be when the request url is hit from the user/slack bot side, so you might wanna look into that. I suspect we have an event type enum with some sort of data passed into the payload?
I think this can be a good reference for fleshing out the logic: https://medium.com/glasswall-engineering/how-to-create-a-slack-bot-using-aws-lambda-in-1-hour-1dbc1b6f021c