Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Function required to be defined locally to run on lambda? #142
Say I create a function called uppercase and deploy it to lambda. It appears if I have lambda installed on a different codebase but provide the correct project.json information, it doesn't work.
but if I do
is now broken. I get --
This seems unintuitive, since my code should now be installed on lambda.
I'd love to be able to keep my deploy and my runtime on two different systems without having the code on both systems.
Is this possible?
We currently prefix functions with the project name by default, so you do need a "valid" project for invocations to work. Without this it would be something like
@tj Thanks for the quick response.
I'm trying to call code that I have deployed to lambda through apex with just the project.json.
The use case for this integrating with existing systems. My assumption is I could write the code to a tmp directory deploy it to lambda, then delete it and call the code later.
@tj as a side note, I tried deleting the /functions/ directory and running
I then re-added the functions directory and tried again and got this: error:
I checked in lambda and I am calling the correct function name that is deployed.
yep the project_function reference won't work yet, since we assume they're defined locally. I'm not sure that's a case we should handle in Apex, I'd like to design things around new deployments not legacy deployments, but I'll leave this open for a while in case anyone else has some feedback. I think your use-case is unique enough that just using the aws cli might make more sense.