-
Notifications
You must be signed in to change notification settings - Fork 421
APIGatewayRestResolver route matching order #2439
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
Comments
Seems like using strip_prefixes in the init parameters like it says in the docs, resolved the issue. |
|
Seems that it didn't help. It might be related to the order in which the functions (with the routing decorators) are defined. |
Looking at this now |
Great finding @royassis, submitting a PR in a few minutes. |
@rubenfonseca is controlling the release date this week but let us know if you can't workaround it now @royassis (I'd say you can given the order of registration as annoying as it is). Thank you so much for taking valuable time to report it (everyone appreciates it!) <3 |
Hey @heitorlessa I can workaround it for now 👍 |
|
This is now released under 2.17.0 version! |
Expected Behaviour
When there are two routes:
And a request is sent to /studies/fetch, the request should be routed to the first endpoint.
Current Behaviour
Request if routed to the second endpoint.
Code snippet
Possible Solution
No response
Steps to Reproduce
Create a SAM project with the snippet as a lambda.
Invoke with /studies/fetch
Powertools for AWS Lambda (Python) version
latest
AWS Lambda function runtime
3.10
Packaging format used
Serverless Application Repository (SAR) App
Debugging logs
No response
The text was updated successfully, but these errors were encountered: