Update shared API instructions #5850
Merged
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
The instructions for shared APIs would always give me errors such as : ``` The CloudFormation template is invalid: Template error: instance of Fn::GetAtt references undefined resource ApiGatewayRestApi ``` After much googling I found https://forum.serverless.com/t/micro-services-with-shared-api-gateway/6486/2 and the solution proposed (deploying the API and exports as their own service) totally worked for me. I thought to update the instructions so more people don't waste hours. Alternatively, if there's a way of making it work the way mentioned, please advise!
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.
What did you implement:
Closes #XXXXX
Update shared API instructions
The instructions for shared APIs (see the 'easiest and ci/cd friendly' section) would always give me errors such as :
After much googling I found https://forum.serverless.com/t/micro-services-with-shared-api-gateway/6486/2 and the solution proposed (deploying the API and exports as their own service) worked for me.
I thought to update the instructions so more people don't waste hours. Alternatively, if there's a way of making it work the way mentioned, please advise!
How did you implement it:
Just changed the markdown
How can we verify it:
Read the markdown
Todos:
Is this ready for review?: YES
Is it a breaking change?: NO