[BREAKING] Move the Lambda Invoke CodePipeline Action #401
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.
This commit moves the Lambda Invoke Action from the codepipeline module to its dedicated,
new lambda-codepipeline module.
It's not possible to move it to the lambda module itself,
as that would cause a cyclic dependency between the codepipeline,
sns and lambda modules.
This continues the refactoring of moving out concrete Action typesfrom the codepipeline module.
Continued from #348
By submitting this pull request, I confirm that my contribution is made under
the terms of the beta license.