Draft
Conversation
🦋 Changeset detectedLatest commit: fb6bc35 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
… each path, and modify test object
…tory containing resource.ts and handler.ts when a new lambda is created from source code
bennettsf
force-pushed
the
defineApi_construct
branch
from
852d34e to
d51586d
Compare
Check package versions Path validation Tests
Implement cognito userpool logic into the construct
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
2 participants
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.
Problem
There is no built-in way in Amplify Gen 2 to define REST APIs using a high-level construct. Developers must manually configure API Gateway, Lambda, and authorization logic. This PR introduces a reusable construct to define REST routes, connect them to Lambda handlers, and optionally protect them with Cognito User Pool authorization.
Issue number, if available:
Changes
Corresponding docs PR, if applicable:
Validation
Checklist
run-e2elabel set.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.