itowlson
itowlson
It's always been a bit flaky (at least, a vault test has, I can never remember its name though!). Are you perceiving that it's getting worse, or is this just...
@PhantomInTheWire Thanks for looking into this! My memory of this issue is that the tests were generally reliable locally, but were flaky enough in GitHub Actions to be annoying (although...
The trouble with using the TLS configs from the outbound networking factor is that they are component specific and available at instance state level, but Postgres uses an app-level connection...
Yeah I started looking at pool-per-component and that seemed okay but then I ran into another problem: the Postgres connection string can contain multiple hosts, but the outbound networking stuff...
It's the tokio-postgres config: https://docs.rs/tokio-postgres/latest/tokio_postgres/config/struct.Config.html#method.get_hosts
The examples (https://docs.rs/tokio-postgres/latest/tokio_postgres/config/struct.Config.html#examples) show multi-host things. I think it's a preference/fallback kind of thing - I can no longer find the docs but I think I saw something saying it...
Okay I think we do handle URL style correctly, because we use the `Config` parser (which handles both connection string and URL style) for permission checking - we never try...
@rylev Agree it makes sense to do this in `main`, but, I wonder if we need to carve out a special case for custom triggers, as these don't pass through...
For this, is the requirement: 1. I kick off an HTTP request, and care nothing for its fate; if I exit a moment later and the server goes "connection dropped,...