I’ve just recently tried Serverless v4 using the new “serverless dev” local development proxying feature. It’s great so far but there’s a behavior I’m uncertain of.
I have a project that throughout various code paths will invoke a lambda in a project that is now SLS v4 but had previously been v3 using serverless offline instead of the new “serverless dev”. In that version if I didn’t have serverless-offline running then my other project would fail to invoke those lambdas. This was a good thing because the calling code needs to know if it called one of these lambdas and succeeded or not.
Now with “serveless dev” I seem to have these “my-project-local-myFunction” proxying lambdas there whether I’m running “serverless dev” or not. So when I run the host project and it attempts to call out to these lambdas it gets a proper response as if it succeeded when in reality nothing ran because I didn’t have “serverless dev” running. The proxy function seems to accept the invocation and do the AWS IOT thing to send a message to my local environment but, as far as I can tell so far, it doesn’t care whether anything is running there to pick up on that or not. It simply looks like the function call succeeded but because nothing ran locally I end up with an incomplete data set for our app and a broken flow.
Should it be working like this? Is there anything I can do to make it work differently?