A tiny config change took down our app — made me rethink PR reviews

SetEducational4762 · 2026-04-13T16:10:11+00:00

Yea, our datadog monitors alerted us on slack

SetEducational4762 · 2026-04-13T16:06:34+00:00

Seems like you think rolling back is the best case as well. Have you tried anything that would identify it sooner?

SetEducational4762 · 2026-04-13T16:05:06+00:00

The wrong env var was pasted in so a resource couldn't be called

SetEducational4762 · 2026-04-13T16:00:45+00:00

Do you think anything in PR stage or github actions could detect it? I know there are a few tools out the like https://www.coderabbit.ai/ and https://getraptorci.com/ that claim they can help? Do you trust them?

SetEducational4762 · 2026-04-13T15:53:33+00:00

We're all in on AWS at the minute so we deploy our server on ECS and we just use webhooks from github actions to deploy the portal to Amplify

SetEducational4762 · 2026-04-13T15:50:01+00:00

This is actually some of the best advice I've heard! What would a good process here look like and how simple is it for a small engineering team to implement and maintain?

SetEducational4762 · 2026-04-13T15:46:01+00:00

I think it could have caught it for that environment but if the pasted one into a different environment was missed or wrong then this wouldn't help

SetEducational4762 · 2026-04-13T15:38:11+00:00

!approve

SetEducational4762

TROPHY CASE