Skip to content

ci: add infra workflow file to main#55

Merged
Androz2091 merged 3 commits into
mainfrom
ci/add-infra-workflow
May 1, 2026
Merged

ci: add infra workflow file to main#55
Androz2091 merged 3 commits into
mainfrom
ci/add-infra-workflow

Conversation

@Androz2091

Copy link
Copy Markdown
Member

Summary

  • Adds `.github/workflows/infra.yml` so `gh workflow run infra.yml` (which requires the workflow to exist on the default branch) can dispatch it.
  • All the Terraform code, tfvars, and IAM bits the workflow consumes live on feat: deploy API + workers to AWS Lambda via Terraform #54. This PR is purely the workflow file.

Why split out

`gh workflow run` against `feat/aws-lambda-deploy` returns 404 because GitHub's workflow_dispatch API only enumerates workflows from the default branch. Landing this file on main first lets us dispatch the workflow with `--ref feat/aws-lambda-deploy` to apply the infra from that branch — and avoids merging the big PR before the infra is up.

Test plan

  • After merge: `gh workflow run infra.yml -f action=plan --ref feat/aws-lambda-deploy` resolves and runs.

GitHub workflow_dispatch only finds workflow files on the default
branch, so this lands infra.yml on main ahead of the larger AWS PR.
The workflow itself does nothing on main — its tfvars and Terraform
code live on feat/aws-lambda-deploy and it's dispatched with --ref
feat/aws-lambda-deploy until that PR merges.
DISCORD_SECRET was removed from the deployment after this branch was
cut, so drop the now-dangling TF_VAR_discord_secret env entry.
@Androz2091 Androz2091 merged commit a8f13b2 into main May 1, 2026
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