Automated patching for arclight using CodePipeline - #1315
Draft
barbarahui wants to merge 12 commits into
Draft
Conversation
barbarahui
changed the title
barbarahui
force-pushed
the
infrastructure-arclight-auto-patching
branch
from
July 1, 2026 22:34
d321374 to
f7965b7
Compare
barbarahui
force-pushed
the
infrastructure-arclight-auto-patching
branch
28 times, most recently
from
July 28, 2026 21:56
eb63841 to
c0fef21
Compare
barbarahui
force-pushed
the
infrastructure-arclight-auto-patching
branch
12 times, most recently
from
July 29, 2026 20:09
83234bd to
267517e
Compare
…anges; This is a no-op change
… docker image as source
barbarahui
force-pushed
the
infrastructure-arclight-auto-patching
branch
from
July 29, 2026 20:34
267517e to
72a423c
Compare
barbarahui
changed the title
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
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.
I did a lot of work on the assumption that we needed to start using codepipeline in order to implement automated patching. However, by the time I got to almost the end, I realized that the complexities of teasing everything apart into different stages is not worth it, at least not for this use case! We may as well continue using CodeBuild for sourcing, building and deploying all in one script. This simpler approach is implemented in #1387
I do basically know how codepipeline works now though, and we can refer back to this code in case we ever want to go this route in the future.