It is a common and suggested use case to use spring data cloud spanner and spanner-jdbc for liquibase for application based database migrations. When you use spring data spanner, one recommended way is to set spring.cloud.gcp.spanner.credentials.encoded-key that contains a base64 encoded service account json to setup authentication.

It would be very beneficial if spring jdbc uses and supports this way of credential providing too. Right now, I workaround by defining a conditional initializer that creates a credentials file on application startup and reference the created file via connection url jdbc:cloudspanner:/projects/my-project/instances/my-instance/databases/my-db;credentials=/path/to/credentials.json.

does it make sense that you also accept the encoded-key via a Connection property, or via some other mechanism that behaves similar to the concept of spring data spanner?

thanks in advance!