lambda: add the possibility for different kind of events in the proxy#5155
Merged
florentinl merged 2 commits intomainfrom Sep 1, 2025
Merged
lambda: add the possibility for different kind of events in the proxy#5155florentinl merged 2 commits intomainfrom
florentinl merged 2 commits intomainfrom
Conversation
5ab3672 to
855f074
Compare
855f074 to
a97f825
Compare
cbeauchesne
requested changes
Aug 28, 2025
cbeauchesne
requested changes
Aug 29, 2025
Collaborator
cbeauchesne
left a comment
There was a problem hiding this comment.
Just a small variable rename, and it should be ok!
cbeauchesne
approved these changes
Aug 29, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
When running python_lambda scenarios, we are currently only serializing events as one kind of lambda events "API Gateway rest events".
The goal of this PR is to enable each weblog to choose which type of events it wants to receive from the
LambdaProxyContainer.Each weblog must have a way to request which event format it wants to receive from the
LambdaProxy, starting with only one addtional event type to validate the design. The goal would be to eventually support all 5 kinds of lambda events that map to an http request:Changes
To do so, I propose adding a mandatory label in the Lambda weblog images that contains the expected type of event:
lambda-proxy.event-type. The scenario then configures the proxy to send the correct type of event.Workflow
🚀 Once your PR is reviewed and the CI green, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist
[<language>], double-check that only<language>is impacted by the changebuild-XXX-imagelabel is present