[TM-1270] CDK-driven Api Gateway implementation. #1
Conversation
This file contains 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
Unfortunately, SAM will not honor an HttpUrlIntegration for local dev, so I've had to create a lambda function that acts as a local proxy to the PHP BE. This makes the AWS implementation of the gateway different from the local implementation, but it should function similarly enough to allow local development to continue without hiccups.
Scriptmatico
approved these changes
Sep 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
https://gfw.atlassian.net/browse/TM-1270
Unfortunately, SAM will not honor an HttpUrlIntegration for local dev, so I've had to create a lambda function that acts as a local proxy to the PHP BE. This makes the AWS implementation of the gateway different from the local implementation, but it should function similarly enough to allow local development to continue without hiccups.
This PR contains a ton of boilerplate and un-interesting config files. The meat of the functionality is in:
README.mdapps/api-gateway/libapps/api-gateway/lambda(local lambda-based proxy, not used in AWS)apps/user-service(very basic scaffolding of a NestJS project that will become the User service)