Skip to content

Enable production API Gateway auto deploy#774

Merged
riddim-developer-bot[bot] merged 1 commit into
mainfrom
chore/prod-api-gateway-autodeploy
Jun 8, 2026
Merged

Enable production API Gateway auto deploy#774
riddim-developer-bot[bot] merged 1 commit into
mainfrom
chore/prod-api-gateway-autodeploy

Conversation

@riddim-developer-bot

Copy link
Copy Markdown
Contributor

What changed

  • Add a production API Gateway activation job to backend-production.yml.
  • Enable auto-deploy for the production HTTP API stage after production route provisioning jobs run.

Why

Production API Gateway has AutoDeploy disabled, so newly created workflow-managed routes can exist in API Gateway but still return 404 through the production custom domain until the stage is manually deployed. The lobbying organization detail routes are already present in the manifest, and rerunning promotion after this change will create and activate them.

Testing

  • actionlint .github/workflows/backend-production.yml
  • Confirmed manifest includes production organization detail routes:
    • GET /api/v1/lobbying/organizations/{id}
    • GET /lobbying/organizations/{id}

@riddim-developer-bot riddim-developer-bot Bot enabled auto-merge (squash) June 8, 2026 20:40
@riddim-developer-bot riddim-developer-bot Bot merged commit 800c298 into main Jun 8, 2026
7 checks passed
@riddim-developer-bot riddim-developer-bot Bot deleted the chore/prod-api-gateway-autodeploy branch June 8, 2026 20:45
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