-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Simple Backend for Lambda #5721
Comments
Hi @aaronclong, that sounds like a reasonable feature. The response would have to be hardcoded of course, both the Lambda-result and the resulting logs. Do you have any preference or ideas on what that could look like? |
@bblommers I am sorry for the late response, a bit behind because of the holidays. I don't have any strong preference. TBH, this library is great, and I rarely have to look under the covers. So, I am not terribly knowledgeable about how to implement this. My only preference would be allowing us to setup a fake lambda easy for No-op runs, and allow us to simulate success/failures. I know that is incredibly vague. Let me know if there is anything I can do to help. |
No problem @aaronclong. Having full flexibility in configuring how the responses look like would be great. Other people have requested this for other operations, so ideally we find a solution that works for every service. But I don't know yet how that's going to look like. |
@aaronclong is this something that you still need? I may have time over next few weeks to implement |
I actually switched jobs and using a different stack. However, I do believe there is value in implementing this. |
I am wonder if the maintainers would be open to creating a simple backend for Lambda? Often, I need to mock invoking Lambda, but I don't need an instance running. It is simple glue code that I don't need test end to end. I just want to assure that I am calling boto3 correctly. Likewise, Docker sometimes is blocked, limited, or general unusable in certain CI environments.
The batch has a
simple_backend
that I am wonder if could be copied/adapted to a Lambda backend.#3997
The text was updated successfully, but these errors were encountered: