|
|
|
|
|
by abrgr
1930 days ago
|
|
Sorry, more investigation prior to mitigation than mitigation. I think moving the lambda aspects of sst to a lambda extension would allow for a workflow like this:
1. Find production issues
2. Replicate production issues in user facing tools
3. Run a local `sst start <fn> --filter '.userId == 'my-user-id'` to have remote <fn> connect to my local for any requests that match `evt.userId == 'my-user-id'`
4. Replicate issue and debug with the request sent to this particular lambda, potentially many calls away from the user action
5. Patch and deploy. Being able to debug in situ would be fairly incredible in a complex application. None of that is meant to take away at all from what you've built. What you have here is really awesome and I'm excited to use it. |
|
Appreciate the feedback!