-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
make next-gen APIGW provider default #11035
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
Conversation
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 3m 43s ⏱️ Results for commit 87154d4. ♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files 2 suites 1h 43m 5s ⏱️ Results for commit 87154d4. ♻️ This comment has been updated with latest results. |
8013d26
to
c30fd63
Compare
a8c26a1
to
50f1fd6
Compare
d2086fb
to
65e70b5
Compare
3178286
to
9282c21
Compare
Currently, only patch changes are allowed on master. Your PR labels (aws:apigateway, semver: minor) indicate that it cannot be merged into the master at this time. |
9282c21
to
478c21d
Compare
478c21d
to
fe564de
Compare
fe564de
to
3fc1684
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Great to see the API GW provider becoming the default! 💯
3fc1684
to
87154d4
Compare
Motivation
This PR makes the APIGW NextProvider to be the default used.
This PR also compiles all PRs done related to this work.
Changes
NG Provider
ANY
request and remove stage from path #11129Follow-up?
TODO
What's left to do:
next_gen
module back into default? TBDOnce this PR is merged: