Updated SQS Processor blueprints#381
Merged
normj merged 1 commit intoaws:masterfrom Feb 7, 2019
austoonz:SQSBlueprint
Merged
Conversation
Member
|
Same comment as the S3 PR. Put each template in a separate folder with its own README file and an entry in the |
Contributor
Author
|
Norm - I have updated this PR as requested.
|
Member
|
Merge to dev branch |
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.
Issue #, if available:
There is no issue related to this.
Description of changes:
Cleaned up wording in the SQS readme file.
The original SQS Processor blueprint included a number of comments to provide a single script that could process a number of different event sources. This made the sample confusing and hard to follow. This PR cleans up the original SQS Processor to only provide the base code sample.
In addition, and to resolve the removal of the additional detail, this PR adds the same S3Event samples from PR 380 so they're available from the S3Event or SQSProcessor blueprints.
This PR also adds an SNS to SQS sample.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.