Skip to content

No replacement for the @LambdaFunction and LambdaInvokerFactory? #2587

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

Open
adworacz opened this issue Jul 12, 2021 · 4 comments
Open

No replacement for the @LambdaFunction and LambdaInvokerFactory? #2587

adworacz opened this issue Jul 12, 2021 · 4 comments
Labels
1.x Parity feature-request A feature should be added or improved. p2 This is a standard priority issue

Comments

@adworacz
Copy link

Expected Behavior

One of the great API improvements provided by the v1 SDK was the LambdaInvokerFactory, which handled so much of the marshalling when directly invoking a Lambda.

There seems to be no v2 replacement that I can find, and nothing is mentioned in the 1.11 to 2.0 changelog which is surprising for something that completely disappeared.

Current Behavior

There is no corollary to the @LambdaFunction and LambdaInvokerFactory set of API utilities.

Possible Solution

Re-implement those utilities.

Context

The amount of boilerplate significantly increases when attempting to call Lambda. This is especially apparent when writing functional tests, where the actual details of invoking a Lambda are not relevant to actually testing that Lambda.

Your Environment

  • AWS Java SDK version used: v2
  • JDK version used: Corretto - 11.0.8
  • Operating System and version: Ubuntu 20.04
@debora-ito
Copy link
Member

Hi @adworacz thank you for reaching out.

We don't have a functionality equivalent to the LambdaInvokerFactory in v2 yet. Let's use this issue to track it.

For anyone who's also interested in seeing this in v2, please add your thumbs up in the original description, it helps us prioritize the requests.

@debora-ito debora-ito added 1.x Parity feature-request A feature should be added or improved. labels Jul 16, 2021
@yasminetalby yasminetalby added the p2 This is a standard priority issue label Nov 18, 2022
aws-sdk-java-automation added a commit that referenced this issue Jun 9, 2023
…eacf6fcf0

Pull request: release <- staging/22e7db0c-7048-456a-a7ed-e47eacf6fcf0
@j-bluemke
Copy link

Hey, I'm working for @simpleshow and we'd like to contribute this feature in case nobody else is working on it. We are currently in the process of switching to v2 and would have to do a whole lot of refactoring without this functionality.

@ionutab
Copy link

ionutab commented Dec 16, 2023

@j-bluemke hmmm, I've just come across this. let me know if there's any chance I could help with this. Thanks!

@aimethed
Copy link

Hello. I know that a large focus of the v2 migration is using the respective client for sending the appropriate requests and this feature does not necessarily align with that. Is this still a feature that is in consideration? Is migrating this feature just a matter of taking the previous LambdaInvokerFactory and updating the references to their v2 equivalents or is there more complicated work to be done?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.x Parity feature-request A feature should be added or improved. p2 This is a standard priority issue
Projects
None yet
Development

No branches or pull requests

6 participants