Skip to content

Add ECR build/deploy pipeline scaffolding for EKS migration - #46

Draft
aravindgee wants to merge 2 commits into
zerodevapp:mainfrom
aravindgee:srep-2737-ecr-pipeline
Draft

Add ECR build/deploy pipeline scaffolding for EKS migration#46
aravindgee wants to merge 2 commits into
zerodevapp:mainfrom
aravindgee:srep-2737-ecr-pipeline

Conversation

@aravindgee

Copy link
Copy Markdown

(Draft, work in progress)

aravindgee and others added 2 commits August 11, 2026 18:07
SREP-2737: draft the GitOps side of the Render -> EKS deployment pipeline,
modeled on doorway-kms's build-push-ecr.yml/verify-staging-image.yml and
3-source ArgoCD values pattern. Reuses the existing Dockerfile as-is; adds
a new ECR-targeting workflow alongside (not replacing) the existing GHCR
build.yaml, since that's still wired into the upstream Alto NPM-publish
flow. Several config values are TODO placeholders pending confirmation
from the team (hostnames, chain config, ElastiCache endpoints).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Per today's SREP-2737 meeting: secrets should be retrieved as files on
the container, not env vars. The CLI has no file-path option for
--executor-private-keys/--utility-private-key, so the shell wrapper now
reads the mounted secret files itself via $(cat ...) instead of
expanding env vars. Keeps SENTRY_DSN/BETTER_STACK_* as env vars since the
app reads those directly from process.env, no CLI flag exists for them.

Also sets replicas: 2, matching the meeting's zero-downtime/multi-replica
cutover requirement (was previously unset, defaulting to the chart's
underlying default).
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