Trigger pipeline regeneration upon organization changes #550
Conversation
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
**Why?** As described in issue awslabs#549. When an account is moved in or out of an organization unit (OU), the pipelines that include that OU are not updated accordingly. **What?** By checking the type of trigger that started this CodePipeline execution, it will force the upload process of the deployment map files when the pipeline was triggered using a StartPipelineExecution API Call. As these are used when the pipeline is instructed to start by a Lambda function that detected an organization unit change. * Add support for --force to the `sync_to_s3.py` helper. * Add `describe_codepipeline_trigger.py` helper to fetch the trigger type of a specific execution. * Set the `--force` as `$EXTRA_OPTS` that are passed to the `sync_to_s3.py` helper if needed. * Allow `aws-deployment-framework-pipelines` CodeBuild container to fetch the `aws-deployment-framework-pipelines` executions.
StewartW
approved these changes
Oct 17, 2022
javydekoning
approved these changes
Oct 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Why?
As described in issue #549. When an account is moved in or out of an organization unit (OU), the pipelines that include that OU are not updated accordingly.
What?
By checking the type of trigger that started this CodePipeline execution, it will force the upload process of the deployment map files when the pipeline was triggered using a StartPipelineExecution API Call. As these are used when the pipeline is instructed to start by a Lambda function that detected an organization unit change.
sync_to_s3.pyhelper.describe_codepipeline_trigger.pyhelper to fetch the trigger type of a specific execution.--forceas$EXTRA_OPTSthat are passed to thesync_to_s3.pyhelper if needed.aws-deployment-framework-pipelinesCodeBuild container to fetch theaws-deployment-framework-pipelinesexecutions.By submitting this pull request, I confirm that you can use, modify, copy, and
redistribute this contribution, under the terms of your choice.