Use Lambda webhook for automated PR creation and merging into reaction-gitops #651
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
…n-gitops Signed-off-by: Grig Gheorghiu <grig@gheorghiu.net>
Signed-off-by: Grig Gheorghiu <grig@gheorghiu.net>
kieckhafer
approved these changes
Jan 28, 2020
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.
Signed-off-by: Grig Gheorghiu grig@gheorghiu.net
Impact: minor
Type: feature
Issue
Automated PRs into the reaction-gitops repo were done via a shell script and required a lot of copy and paste across CircleCI config.yml files in our repos.
Solution
Use a CirlcleCI Orb which sends the PR payload to a Lambda webhook deployed in one of our internal AWS environments.
Testing
When a PR gets merged into the release-v3.0.0 there should be an automated PR created and merged into the reaction-gitops repo.