This repository was archived by the owner on Oct 22, 2021. It is now read-only.
Build API Gateway resources into CF template #1
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
The current README.md describes what manual steps need to be done in AWS Console to set up an API Gateway suitable for this project. However, since the inception of this project, CloudFormation has come to support API Gateway resources. This pull request revises the CloudFormation template to automate the manual API Gateway steps that had been described in the README.md.
Also, CloudFormation templates that deploy lambda functions with runtime=nodejs are no longer allowed. I've updated the template to runtime=nodejs4.3.