lightbody
commented
5 years ago With the help of @jameskleeh, I was able to accomplish this without any changes to the source of this project:
import io.micronaut.configuration.jdbc.hikari.DatasourceConfiguration;
import io.micronaut.context.event.BeanInitializedEventListener;
import io.micronaut.context.event.BeanInitializingEvent;
import javax.inject.Singleton;
@Singleton
public class UnixSocketDatasourceConfigurationListener implements BeanInitializedEventListener<DatasourceConfiguration> {
private static final String REF = "://socket@";
@Override
public DatasourceConfiguration onInitialized(BeanInitializingEvent<DatasourceConfiguration> event) {
DatasourceConfiguration config = event.getBean();
// check if the URL appears to point to a unix socket
String url = config.getUrl();
int start = url.indexOf(REF);
if (start != -1) {
String socketPath = url.substring(start + REF.length());
config.setUrl(url.substring(0, start) + ":///");
config.addDataSourceProperty("socketFactory", UnixSocketFactory.class.getName());
config.addDataSourceProperty("socketFactoryArg", socketPath);
}
return config;
}
}import jnr.unixsocket.UnixSocketAddress;
import jnr.unixsocket.UnixSocketChannel;
import javax.net.SocketFactory;
import java.io.File;
import java.io.IOException;
import java.net.InetAddress;
import java.net.Socket;
import java.net.UnknownHostException;
public class UnixSocketFactory extends SocketFactory {
private String socket;
public UnixSocketFactory(String socket) {
this.socket = socket;
}
@Override
public Socket createSocket() throws IOException {
return UnixSocketChannel.open(new UnixSocketAddress(new File(socket))).socket();
}
@Override
public Socket createSocket(String s, int i) throws IOException, UnknownHostException {
throw new UnsupportedOperationException();
}
@Override
public Socket createSocket(String s, int i, InetAddress inetAddress, int i1) throws IOException, UnknownHostException {
throw new UnsupportedOperationException();
}
@Override
public Socket createSocket(InetAddress inetAddress, int i) throws IOException {
throw new UnsupportedOperationException();
}
@Override
public Socket createSocket(InetAddress inetAddress, int i, InetAddress inetAddress1, int i1) throws IOException {
throw new UnsupportedOperationException();
}
}With these two classes, your application.yml file can look like this:
datasources:
default:
url: jdbc:postgresql://socket@/path/to/project-id:us-central1:instance-name/.s.PGSQL.5432
username: postgres
password: passwordAs you can see, I introduced a simple new convention that looks for "socket@" and establishes the UnixSocketFactory if so. Otherwise, it keeps the same Hikari default behavior that connects to hosts via TCP/IP.
On Google Cloud Run the socket path will start with /cloudsql/ and for local development you can use the Google Cloud SQL Proxy like so to keep the same path:
./cloud_sql_proxy -dir /cloudsqlFeel free to close this out... or use it as inspiration for an improvement to this project. I suspect others who try to use Cloud Run + Cloud SQL will bump into similar issues.
kurtisvg
glaforge
shahmirn
luisospina-sealed
I've decided to use managed Google Cloud Run + a Google SQL Postgres database for my deployment. The docs are pretty sparse, but the way you can integrate the two securely without having to keep your database open to the public is to follow the directions outlined here.
As you can see, the trick is that Cloud Run bakes in a little unix socket that proxies the connection to the database. You can also recreate this same behavior by running the proxy locally.
Unix sockets aren't native to Java and thus the
SocketFactoryneeds to be overrides. At first Google's docs suggested to me that their provided SocketFactory was what I needed.But after lots of testing, I've realized it does more than I need, such as authentication that has actually already been done once the proxy is established. Really all I needed was to override the
SocketFactoryand return ajnr.unixsocket.UnixSocketpointing to:/cloudsql/project-id:us-central1:instance-name/.s.PGSQL.5432And that does the trick, both for local development and in Cloud Run. Woo hoo!
Unfortunately, my problem is that the Micronaut SQL factories don't seem to give me the control I need to establish a custom
SocketFactory. I'm pretty new to Micronaut, so I'm guessing it is very possible that it can be done via configuration, but I've yet to figure out how to invokeHikariConfig.addDataSourceProperty("socketFactory", "my.custom.SocketFactory")viaapplication.yml.So this issue could be one of a few things:
Thanks!