Conrad Ludgate 24d6587914 chore(proxy): refactor self-signed config (#10154) ...

## Problem

While reviewing #10152 I found it tricky to actually determine whether
the connection used `allow_self_signed_compute` or not.

I've tried to remove this setting in the past:
* https://github.com/neondatabase/neon/pull/7884
* https://github.com/neondatabase/neon/pull/7437
* https://github.com/neondatabase/cloud/pull/13702

But each time it seems it is used by e2e tests

## Summary of changes

The `node_info.allow_self_signed_computes` is always initialised to
false, and then sometimes inherits the proxy config value. There's no
need this needs to be in the node_info, so removing it and propagating
it via `TcpMechansim` is simpler.

2024-12-16 11:15:25 +00:00

..

client

chore(proxy): refactor self-signed config (#10154)

2024-12-16 11:15:25 +00:00

errors.rs

proxy: Refactor cplane types (#9643)

2024-11-05 23:03:53 +01:00

messages.rs

chore(proxy): remove code for old API (#10109)

2024-12-12 13:42:50 +00:00

mgmt.rs

proxy: Replace "web(auth)" with "console redirect" everywhere (#9655)

2024-11-06 11:03:38 +00:00

mod.rs

chore(proxy): refactor self-signed config (#10154)

2024-12-16 11:15:25 +00:00