Generalize sorting Lambda buildspec for mission deploys#9
Draft
jamesray wants to merge 1 commit into
Draft
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
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.
Summary
MISSION_NAME.MISSION_NAME,LAMBDA_PIPELINE=SORTING, and the image tag into the architecture build so deployments can be driven automatically again.Why
The sorting buildspec was hard-coded to the original HERMES deployment path. This makes it awkward to reuse the same build automation for additional missions. This change makes the build/deploy handoff mission-aware while keeping the HERMES default intact.
Validation
buildspec.ymlas YAML with Ruby.git diff --check.BASE_IMAGEbuild arg.