feat: Add a flag to ALBResolver to URL-decode query parameters#7940
Conversation
|
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need. |
tests/functional/event_handler/_pydantic/test_openapi_validation_middleware.py
Show resolved
Hide resolved
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #7940 +/- ##
===========================================
- Coverage 96.72% 96.72% -0.01%
===========================================
Files 278 278
Lines 13607 13626 +19
Branches 1080 1083 +3
===========================================
+ Hits 13162 13180 +18
Misses 327 327
- Partials 118 119 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Hey @chriselion I'm attending some internal training and will review this PR later this week. Thanks a lot for working on this. |
|
leandrodamascena
left a comment
There was a problem hiding this comment.
Hey @chriselion thanks a lot for working on this! APPROVED!!!
8761fe7
into
aws-powertools:develop
|
Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience! |



Issue number: closes #7621
Summary
From https://docs.aws.amazon.com/elasticloadbalancing/latest/application/lambda-functions.html, for ALB requests
This adds a flag to ALBResolver to decode the query parameters before they are validated.
Changes
decode_query_parametersflag toALBResolverinitializer.decode_query_parameterstoALBEvent. This defaults to false.**kwargsargument to theBaseProxyEventinitializers, but didn't love that.ALBResolver._to_proxy_event(overrides the parent method). This calls the parent method, and sets a decode_query_parameters flag on the resulting ALBEvent.User experience
No change to the user experience - default behavior is the same, and users have to opt-in to get the new behavior.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.