(Opening this issue based on a question asked on Discord)
Currently the SQLx connection pool provisioned by shuttle-shared-db uses native-tls to establish a secure connection to the database server.
Would it be thinkable to gate these behind features like rustls and native-tls, where one of them is set as the default? (this would be a breaking change)
Looking at the SQLx source code, they use the webpki-roots certificates for their trust anchors.
So if Shuttle installs their own CA certificates, using the rustls feature will break it.
(Opening this issue based on a question asked on Discord)
Currently the SQLx connection pool provisioned by
shuttle-shared-dbusesnative-tlsto establish a secure connection to the database server.Would it be thinkable to gate these behind features like
rustlsandnative-tls, where one of them is set as the default? (this would be a breaking change)Looking at the SQLx source code, they use the
webpki-rootscertificates for their trust anchors.So if Shuttle installs their own CA certificates, using the
rustlsfeature will break it.