Closed jsonfry closed 1 month ago
fixes #320
Is this likely to progress any further?
seems reasonable to me. a test to make sure this works / does not regress would be useful. @sebsto ?
@swift-server-bot test this please
Thank you @jsonfry for submitting this PR.
What happens when LOCAL_LAMBDA_SERVER_INVOCATION_ENDPOINT
is not defined ?
@tomerd I think it's a valid use case and we should support the runtime interface emulator.
What happens when LOCAL_LAMBDA_SERVER_INVOCATION_ENDPOINT is not defined ?
Lambda.env("LOCAL_LAMBDA_SERVER_INVOCATION_ENDPOINT")
returns nil
, so eventually this line of code is reached: self.invocationEndpoint = invocationEndpoint ?? "/invoke"
and it's set to /invoke
, as before.
Or in short, it behaves as it did before.
Oh, I missed that line of code. Good for me then.
@tomerd feel free to approve when you have time - thanks
@swift-server-bot test this please
UPDATE : looks like I don't have permissions to trigger a CI test and without test, I can not merge :-(
@tomerd can you trigger a set of test. Apparently, I don't have permissions to do so. Thanks
@swift-server-bot test this please
Allow the changing of the local lambda server's invocation endpoint
Motivation:
[Explain here the context, and why you're making that change. What is the problem you're trying to solve.]
As described in https://github.com/swift-server/swift-aws-lambda-runtime/issues/320 I want to be able to use other tooling that expects the local invocation endpoint to have a specific path, not just
/invoke
.Modifications:
I have added an envionrment variable option that lets you override the invocation endpoint url.
Result:
If you set LOCAL_LAMBDA_SERVER_ENABLED to run locally, you can now also set LOCAL_LAMBDA_SERVER_INVOCATION_ENDPOINT to any value to change the path, e.g. to
/2015-03-31/functions/function/invocations
to match how the "runtime interface emulator" works.