Skip to content

Generalize sorting Lambda buildspec for mission deploys#9

Draft
jamesray wants to merge 1 commit into
mainfrom
jamesray/mission-buildspec-automation
Draft

Generalize sorting Lambda buildspec for mission deploys#9
jamesray wants to merge 1 commit into
mainfrom
jamesray/mission-buildspec-automation

Conversation

@jamesray

Copy link
Copy Markdown

Summary

  • Generalizes the sorting Lambda CodeBuild buildspec around MISSION_NAME.
  • Keeps HERMES as the default behavior while allowing mission-specific ECR repo names and base images.
  • Passes 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

  • Parsed buildspec.yml as YAML with Ruby.
  • Ran git diff --check.
  • Confirmed the Dockerfile accepts the BASE_IMAGE build arg.
  • Scanned the changed file for high-confidence credentials; no AWS keys, GitHub tokens, Slack tokens, or private keys found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant