Skip to content

Conversation

@patriot1burke
Copy link
Contributor

@patriot1burke patriot1burke commented May 20, 2020

Fixes: #9395

@patriot1burke
Copy link
Contributor Author

/cc @miron4dev @arturs-cc

lambda client context impl

decode base64 header

undo base64

lambda process resources
@patriot1burke patriot1burke force-pushed the lambda-clientcontext branch from 4324013 to 259758b Compare May 20, 2020 20:21
@patriot1burke
Copy link
Contributor Author

@gsmet This build failure is ok. Maven build passed for that one CI failure.

Copy link
Contributor

@geoand geoand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@geoand geoand merged commit 6141a5a into quarkusio:master May 21, 2020
@gsmet gsmet changed the title Read Lambda ClientContext correctly, Issue #9395 Read Lambda ClientContext correctly May 26, 2020
@gsmet gsmet added this to the 1.5.0.Final milestone May 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Parsing clientContext header seems to be broken in quarkus-amazon-lambda extension

3 participants