Skip to content

feat(deploy): add single deploy script and manual CI workflow - #128

Draft
prdai wants to merge 2 commits into
mainfrom
feat/issue-40-aws-approach
Draft

prdai wants to merge 2 commits into
mainfrom
feat/issue-40-aws-approach

Conversation

@prdai

@prdai prdai commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

what changed

  • Added scripts/deploy.sh, a dependency-ordered entrypoint for both trees. It derives queue URLs and ARNs, table names, bucket names, role ARNs, and the default VPC from CloudFormation outputs, and looks up regional ACM certificates by hostname.
  • Added .github/workflows/deploy.yml, manual workflow_dispatch only, with OIDC auth and tree, unit, dry-run, and registry-image inputs.
  • Independent units now deploy in dependency-ordered parallel waves (--jobs 4, --sequential to disable). The runner is a 2 vCPU arm64 instance; the heavy eif-build-base cargo step gets the runner to itself.
  • Included the secure registry-service image build and ship, running natively on arm64.
  • Added docs/deploy.md and linked it from the README and getting-started guide.

why

Deploys were manual per service and the CloudFormation stacks lived in separate sub-Makefiles. This gives one path for both trees and a manual CI run, with no merge trigger.

verification

  • bash -n and shellcheck pass on scripts/deploy.sh.
  • yamllint passes except the same on: truthy warning the existing ci.yml has.
  • actionlint passes apart from the custom Blacksmith runner label.
  • Exercised list, argument validation, dependency order, .env generation, and wave parallelism in an isolated copy (independent units start together; dependents wait).
  • Not verified: a live AWS deploy. It needs the OIDC role, four secrets, fleet variables, the JWT signing key in SSM, and a running CSAV instance.

notes

  • EXECUTION_HOST_RADS has no default and must be set before deploying the rads tree.
  • --jobs 4 on a 2 vCPU runner is safe because deploys are AWS-bound, but bump the runner to blacksmith-4vcpu-ubuntu-2404-arm if the cargo image build needs more headroom.
  • The registry image builds on arm64 natively. Blacksmith's Docker layer cache is not wired because the Dockerfile's base images are built locally.

Closes #40

prdai and others added 2 commits November 19, 2026 20:48
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.

ci: single deploy script and deploy-on-merge pipeline

1 participant