Support Non HTTP TCP Traffic in Codex Environments

Part of my environment setup requirements require end to end tests to our postgres database.

This is currently not possible since all traffic in the codex environment is routed through the http proxy.

Since postgres doesn’t use http (it uses a custom protocol over TCP), the traffic is blocked.

This makes codex unusable for any applications that require database connectivity for real world testing.

I would say we should just use sqlite to run tests, but the syntax we have is not compatible with sqlite. It’s postgres specific.

Now I guess my only option is to deploy a full blown postgres DB inside of the codex environment…? Which I’d rather not add to our deployment complexity.

1 Like