Add clean-up of stale deployment map files in the pipeline bucket #562
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?
The identify-out-of-date-pipelines process will iterate over the S3 files and delete the stale pipelines that are no longer defined.
However, if you delete a deployment map file, the old deployment map would still exist in the pipelines bucket. Which will put the identify-out-of-date-pipeline process in the wrong direction, as it will think that these pipelines are still active.
What?
Instructing the sync to S3 process to delete stale files in the S3 bucket, so deleted deployment map files are also deleted in the pipeline bucket.
By submitting this pull request, I confirm that you can use, modify, copy, and
redistribute this contribution, under the terms of your choice.