Service and stage prefix on Lambda function names #8
Description
I'm not sure if this is a serverless-offline-lambda issue or maybe serverless-offline so please feel free to point me in the right direction.
I've gotten this working (after I realised that the Lambda endpoint seems to be hard coded to localhost:4000 rather than being set in serverless.yml like say serverless-s3-local is) however I get different results when running locally than I do after deploying.
When running locally I need to specify the Lambda function name as myfunction but when running on AWS I need to call it as myservice-stage-myfunction.
Is there any way to prefix the Lambda function name with the service and stage so that calling it locally uses the same full name as you use on AWS after deployment?
Apologies if I'm missing something as I'm a bit new to all this.