Div Arora

You can use any mechanism supported by the aws sdk, which are documented at https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/configuring-the-jssdk.html In this specific scenario, you could use e.g. environment variables on your container definition. Or...

I'd much rather have a CI check for this rather than husky running on every commit. It's also the standard approach we're using across the org.

Instead of needing to support different frameworks etc here, would placing this service and your other ones behind a reverse proxy do the trick?

Thanks for the report @SpareShade , we'll try to have this fixed soon. I'm guessing it'll be fixed for newer projects; an in-place migration for existing ones will likely be...

How about instead we start using the commit convention we use in the rest of our repos, and version off that? Only building on `common.vars.json` has the downside of not...

That's basically it-the older AMIs don't disable IPv6, so having that entry in /etc/hosts doesn't present a problem. We should definitely fix the AMI; in the interim, if you want...

Go for it, no concerns

re-opening; was closed by automation when a fix was pushed to staging

Hmm at least for liveness/health checks, we'd want to be hitting the postgrest instances directly, rather than going through nginx or a similar rewriting layer. Even with an nginx setup,...

(Just a note for any observers; there are some flaws with the methodology used for the above numbers, we'll be updating them soon)