event rule to stop codepipeline first run (rMain only for now) #261
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
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.
Description of changes:
For some reason CodePipeline starts newly-created pipelines automatically. In SDLF this means they are usually failing, especially because source branches are not available yet: AWS::CodeCommit::Repository does not allow creating more than one branch through the
Codeparameter, so when creating pipelines for all environments (dev, test and main branches),devandtestwould fail.Even if these branches existed the content would need to be relevant to not fail in later stages of the pipelines.
This is confusing for users as these failures are not relevant. This PR adds an event rule and a Lambda function to stop CodePipelines as soon as they start their first run. This is a solution, not a great solution, but let's improve things bit by bit.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.