Skip to content

Commit

Permalink
feat: Spring Cloud AlloyDB integration (#2787) (#2788)
Browse files Browse the repository at this point in the history
* feat: Spring Cloud AlloyDB integration

* chore: add empty line

* chore: code review
  • Loading branch information
ttosta-google authored Apr 23, 2024
1 parent b1e87b3 commit 67d994e
Show file tree
Hide file tree
Showing 31 changed files with 1,334 additions and 1 deletion.
1 change: 1 addition & 0 deletions .github/workflows/NativeTests.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ jobs:
fail-fast: false
matrix:
it:
- alloydb-sample
- bigquery-sample
- bigquery
- core
Expand Down
1 change: 1 addition & 0 deletions .github/workflows/compatibilityCheck.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ jobs:
fail-fast: false
matrix:
it:
- alloydb
- bigquery
- cloudsql
- config
Expand Down
1 change: 1 addition & 0 deletions .github/workflows/integrationTests.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,7 @@ jobs:
fail-fast: false
matrix:
it:
- alloydb
- bigquery
- cloudsql
- config
Expand Down
149 changes: 149 additions & 0 deletions docs/src/main/asciidoc/alloydb.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,149 @@
[#alloydb]
== AlloyDB

Spring Framework on Google Cloud adds integrations with
https://docs.spring.io/spring/docs/current/spring-framework-reference/html/jdbc.html[Spring JDBC], so you can run your PostgreSQL databases in https://cloud.google.com/alloydb[Google AlloyDB] using Spring JDBC.

The AlloyDB support is provided by Spring Framework on Google Cloud in the form of a Spring Boot AlloyDB starter for PostgreSQL.
The role of the starters is to read configuration from properties and assume default settings so that user experience connecting to PostgreSQL is as simple as possible.

=== JDBC Support
Maven and Gradle coordinates, using <<getting-started.adoc#bill-of-materials, Spring Framework on Google Cloud BOM>>:

[source,xml]
----
<dependency>
<groupId>com.google.cloud</groupId>
<artifactId>spring-cloud-gcp-starter-alloydb</artifactId>
</dependency>
----

[source,subs="normal"]
----
dependencies {
implementation("com.google.cloud:spring-cloud-gcp-starter-alloydb")
}
----

==== Prerequisites

In order to use the Spring Boot Starters for Google AlloyDB, the Google AlloyDB API must be enabled in your Google Cloud project.

To do that, go to the https://console.cloud.google.com/apis/library[API library page] of the Google Cloud Console, search for "AlloyDB API" and enable the option that is called "AlloyDB API" .


==== Spring Boot Starter for Google AlloyDB

The Spring Boot Starters for Google AlloyDB provide an autoconfigured https://docs.oracle.com/javase/7/docs/api/javax/sql/DataSource.html[`DataSource`] object.
Coupled with Spring JDBC, it provides a
https://docs.spring.io/spring/docs/current/spring-framework-reference/html/jdbc.html#jdbc-JdbcTemplate[`JdbcTemplate`] object bean that allows for operations such as querying and modifying a database.

[source,java]
----
public List<Map<String, Object>> listUsers() {
return jdbcTemplate.queryForList("SELECT * FROM user;");
}
----

You can rely on
https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-sql.html#boot-features-connect-to-production-database[Spring Boot data source autoconfiguration] to configure a `DataSource` bean.
In other words, properties like the username, `spring.datasource.username`, and password, `spring.datasource.password` can be used.
There is also some configuration specific to Google AlloyDB (see "AlloyDB Configuration Properties" section below).

|===
| Property name | Description | Required | Default value
| `spring.datasource.username` | Database username | No | `postgres`
| `spring.datasource.password` | Database password | No | `null`
| `spring.datasource.driver-class-name` | JDBC driver to use. | No | `org.postgresql.Driver`
|===

NOTE: If you provide your own `spring.datasource.url`, it will be ignored, unless you disable AlloyDB autoconfiguration with `spring.cloud.gcp.alloydb.enabled=false`.

===== `DataSource` creation flow

Spring Boot starter for Google AlloyDB registers an `AlloyDbEnvironmentPostProcessor` that provides a correctly formatted `spring.datasource.url` property to the environment based on the properties mentioned above.
It also provides defaults for `spring.datasource.username` and `spring.datasource.driver-class-name`, which can be overridden.
The starter also configures credentials for the JDBC connection based on the AlloyDB properties below.

The user properties and the properties provided by the `AlloyDbEnvironmentPostProcessor` are then used by https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-sql.html[Spring Boot] to create the `DataSource`.
You can select the type of connection pool (e.g., Tomcat, HikariCP, etc.) by https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-sql.html#boot-features-connect-to-production-database[adding their dependency to the classpath].

Using the created `DataSource` in conjunction with Spring JDBC provides you with a fully configured and operational `JdbcTemplate` object that you can use to interact with your AlloyDB database.
You can connect to your database with as little as a database and instance names.

=== AlloyDB IAM database authentication

Currently, AlloyDB supports https://cloud.google.com/alloydb/docs/manage-iam-authn[IAM database authentication].
It allows you to connect to the database using an IAM account, rather than a predefined database username and password.
You will need to do the following to enable it:

. In your AlloyDB instance settings, turn on the `alloydb.iam_authentication` flag.
. Add the IAM user or service account to the list of cluster users.
. In the application settings, set `spring.cloud.gcp.alloydb.enable-iam-auth` to `true`. Note that this will also set the database protocol `sslmode` to `disabled`, as it's required for IAM authentication to work.
However, it doesn't compromise the security of the communication because the connection is always encrypted.
. Set `spring.datasource.username` to the IAM user or service account created in step 2. Note that IAM user or service account still needs to be https://www.postgresql.org/docs/current/sql-grant.html[granted permissions] before modifying or querying the database.

=== AlloyDB Configuration Properties

|===
| Property name | Description | Required | Default value
| `spring.cloud.gcp.alloydb.enabled` | Enables or disables AlloyDB auto configuration | No | `true`
| `spring.cloud.gcp.alloydb.database-name` | The name of the database to connect to. | Yes |
| `spring.cloud.gcp.alloydb.instance-connection-uri` | The Google AlloyDB instance connection URI. | Yes |
For example, `projects/PROJECT_ID/locations/REGION_ID/clusters/CLUSTER_ID/instances/INSTANCE_ID`.
| `spring.cloud.gcp.alloydb.ip-type` | Specifies a preferred IP type for connecting to a AlloyDB instance. (`PUBLIC`, `PRIVATE`, `PSC`) | No | `PRIVATE`
| `spring.cloud.gcp.alloydb.enable-iam-auth` | Specifies whether to enable IAM database authentication. | No | `False`
| `spring.cloud.gcp.alloydb.admin-service-endpoint` | An alternate AlloyDB API endpoint. | No |
| `spring.cloud.gcp.alloydb.quota-project` | The project ID for quota and billing. | No |
| `spring.cloud.gcp.alloydb.target-principal` | The service account to impersonate when connecting to the database and database admin API. | No |
| `spring.cloud.gcp.alloydb.delegates` | A comma-separated list of service accounts delegates. | No |
| `spring.cloud.gcp.alloydb.named-connector` | The name of the named connector. | No |
| `spring.cloud.gcp.alloydb.credentials.location` | File system path to the Google OAuth2 credentials private key file.
Used to authenticate and authorize new connections to a Google AlloyDB instance. | No
|===

NOTE: You need to run your application from a VM within the created VPC to connect to AlloyDB using its private IP.
To connect using Public IP, enable the AlloyDB instance's for external connections
following https://cloud.google.com/alloydb/docs/connect-public-ip[these instructions] and
add `spring.cloud.gcp.alloydb.ip-type=PUBLIC` to your `application.properties`.

=== Troubleshooting tips

[#connection-issues]
==== Connection issues
If you're not able to connect to a database and see an endless loop of `Connecting to AlloyDB instance [...] on IP [...]`, it's likely that exceptions are being thrown and logged at a level lower than your logger's level.
This may be the case with HikariCP, if your logger is set to INFO or higher level.

To see what's going on in the background, you should add a `logback.xml` file to your application resources folder, that looks like this:

[source, xml]
----
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<include resource="org/springframework/boot/logging/logback/base.xml"/>
<logger name="com.zaxxer.hikari.pool" level="DEBUG"/>
</configuration>
----

==== PostgreSQL: `java.net.SocketException: already connected` issue

We found this exception to be common if your Maven project's parent is `spring-boot` version `1.5.x`, or in any other circumstance that would cause the version of the `org.postgresql:postgresql` dependency to be an older one (e.g., `9.4.1212.jre7`).

To fix this, re-declare the dependency in its correct version.
For example, in Maven:

[source,xml]
----
<dependency>
<groupId>org.postgresql</groupId>
<artifactId>postgresql</artifactId>
<version>42.7.3</version>
</dependency>
----

=== Samples

Available sample applications and codelabs:

- https://github.com/GoogleCloudPlatform/spring-cloud-gcp/tree/main/spring-cloud-gcp-samples/spring-cloud-gcp-alloydb-sample[Spring Framework on Google Cloud AlloyDB]
- Codelab: https://codelabs.developers.google.com/create-alloydb-database-with-cloud-run-job[Creating AlloyDB database with Cloud Run Job]
7 changes: 7 additions & 0 deletions docs/src/main/asciidoc/getting-started.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,10 @@ Refer for the full list https://github.com/GoogleCloudPlatform/spring-cloud-gcp/
| Provides a security layer over applications deployed to Firebase
| <<security-firebase.adoc#security-firebase, com.google.cloud:spring-cloud-gcp-starter-security-firebase>>

| AlloyDB
| AlloyDB integrations with PostgreSQL
| <<alloydb.adoc#alloydb, com.google.cloud:spring-cloud-gcp-starter-alloydb>>

|===

==== Spring Initializr
Expand Down Expand Up @@ -186,6 +190,9 @@ https://github.com/GoogleCloudPlatform/spring-cloud-gcp/tree/main/spring-cloud-g

| Cloud Security - Firebase
| https://github.com/GoogleCloudPlatform/spring-cloud-gcp/tree/main/spring-cloud-gcp-samples/spring-cloud-gcp-security-firebase-sample[spring-cloud-gcp-security-firebase-sample]

| AlloyDB
| https://github.com/GoogleCloudPlatform/spring-cloud-gcp/tree/main/spring-cloud-gcp-samples/spring-cloud-gcp-alloydb-sample[spring-cloud-gcp-alloydb-sample]
|===

Each sample application demonstrates how to use Spring Framework on Google Cloud libraries in context and how to setup the dependencies for the project.
Expand Down
2 changes: 2 additions & 0 deletions docs/src/main/asciidoc/index.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,8 @@ include::cloudfoundry.adoc[]

include::kotlin.adoc[]

include::alloydb.adoc[]

== Configuration properties

To see the list of all Google Cloud related configuration properties please check link:appendix.html[the Appendix page].
Expand Down
5 changes: 5 additions & 0 deletions docs/src/main/asciidoc/sagan-index.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ Project features include:
* Spring Data Cloud Datastore
* Spring Data Reactive Repositories for Cloud Firestore
* Spring Data Cloud SQL
* Spring Data AlloyDB
* Google Cloud Logging & Tracing
* Google Cloud Storage (Spring Resource and Spring Integration)
* Google Cloud Vision API Template
Expand Down Expand Up @@ -100,6 +101,10 @@ A sample of these artifacts are provided below.
| Extracts IAP identity information from applications deployed to Firebase
| `com.google.cloud:spring-cloud-gcp-starter-security-firebase`

| AlloyDB
| AlloyDB integrations with PostgreSQL
| `com.google.cloud:spring-cloud-gcp-starter-alloydb`

|===

== Code Samples
Expand Down
6 changes: 6 additions & 0 deletions spring-cloud-gcp-autoconfigure/pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -298,6 +298,12 @@
</exclusions>
</dependency>

<!-- AlloyDB -->
<dependency>
<groupId>com.google.cloud</groupId>
<artifactId>alloydb-jdbc-connector</artifactId>
</dependency>

<!-- Config -->
<dependency>
<groupId>org.springframework.cloud</groupId>
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,155 @@
/*
* Copyright 2024 Google LLC
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* https://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/

package com.google.cloud.spring.autoconfigure.alloydb;

import com.google.cloud.alloydb.ConnectorRegistry;
import java.util.HashMap;
import java.util.Map;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.context.properties.ConfigurationProperties;
import org.springframework.boot.context.properties.bind.Binder;
import org.springframework.boot.context.properties.bind.PlaceholdersResolver;
import org.springframework.boot.context.properties.bind.PropertySourcesPlaceholdersResolver;
import org.springframework.boot.context.properties.source.ConfigurationPropertySources;
import org.springframework.boot.env.EnvironmentPostProcessor;
import org.springframework.core.env.ConfigurableEnvironment;
import org.springframework.core.env.Environment;
import org.springframework.core.env.MapPropertySource;
import org.springframework.util.ClassUtils;
import org.springframework.util.StringUtils;

/**
* Provides Google AlloyDB instance connectivity through Spring JDBC by
* providing only a database and instance connection URI.
*/
public class AlloyDbEnvironmentPostProcessor implements EnvironmentPostProcessor {

private static final String JDBC_URL_TEMPLATE = "jdbc:postgresql:///%s?socketFactory=com.google.cloud.alloydb.SocketFactory";
private static final String JDBC_DRIVER_CLASS = "org.postgresql.Driver";
private static final String DEFAULT_USERNAME = "postgres";

@Override
public void postProcessEnvironment(
ConfigurableEnvironment environment, SpringApplication application) {

if (environment.getPropertySources().contains("bootstrap")) {
// Do not run in the bootstrap phase as the user configuration is not available
// yet
return;
}

boolean isAlloyDbEnabled = Boolean.parseBoolean(environment.getProperty("spring.cloud.gcp.alloydb.enabled", "true"));
if (!isAlloyDbEnabled) {
return;
}

String propertiesPrefix = AlloyDbProperties.class.getAnnotation(ConfigurationProperties.class).value();
AlloyDbProperties alloyDbProperties = new Binder(
ConfigurationPropertySources.get(environment),
new NonSecretsManagerPropertiesPlaceholdersResolver(environment),
null,
null,
null)
.bind(propertiesPrefix, AlloyDbProperties.class)
.orElse(new AlloyDbProperties());

if (isOnClasspath("com.google.cloud.alloydb.SocketFactory")
&& isOnClasspath(JDBC_DRIVER_CLASS)) {
// configure default JDBC driver and username as fallback values when not
// specified
Map<String, Object> fallbackMap = new HashMap<>();
fallbackMap.put("spring.datasource.username", DEFAULT_USERNAME);
fallbackMap.put(
"spring.datasource.driver-class-name", JDBC_DRIVER_CLASS);
environment
.getPropertySources()
.addLast(new MapPropertySource("ALLOYDB_DATA_SOURCE_FALLBACK", fallbackMap));

// always set the spring.datasource.url property in the environment
Map<String, Object> primaryMap = new HashMap<>();
primaryMap.put("spring.datasource.url", getJdbcUrl(alloyDbProperties));
environment
.getPropertySources()
.addFirst(new MapPropertySource("ALLOYDB_DATA_SOURCE_URL", primaryMap));
}

// support usage metrics
ConnectorRegistry.addArtifactId(
"spring-cloud-gcp-alloydb/" + this.getClass().getPackage().getImplementationVersion());
}

private String getJdbcUrl(AlloyDbProperties properties) {
String jdbcUrl = String.format(JDBC_URL_TEMPLATE, properties.getDatabaseName());

if (StringUtils.hasText(properties.getInstanceConnectionUri())) {
jdbcUrl += "&alloydbInstanceName=" + properties.getInstanceConnectionUri();
}

if (StringUtils.hasText(properties.getIpType())) {
jdbcUrl += "&alloydbIpType=" + properties.getIpType();
}

if (properties.isEnableIamAuth()) {
jdbcUrl += "&alloydbEnableIAMAuth=true&sslmode=disable";
}

if (StringUtils.hasText(properties.getAdminServiceEndpoint())) {
jdbcUrl += "&alloydbAdminServiceEndpoint=" + properties.getAdminServiceEndpoint();
}

if (StringUtils.hasText(properties.getQuotaProject())) {
jdbcUrl += "&alloydbQuotaProject=" + properties.getQuotaProject();
}

if (StringUtils.hasText(properties.getTargetPrincipal())) {
jdbcUrl += "&alloydbTargetPrincipal=" + properties.getTargetPrincipal();
}

if (StringUtils.hasText(properties.getDelegates())) {
jdbcUrl += "&alloydbDelegates=" + properties.getDelegates();
}

if (StringUtils.hasText(properties.getNamedConnector())) {
jdbcUrl += "&alloydbNamedConnector=" + properties.getNamedConnector();
}

return jdbcUrl;
}

private boolean isOnClasspath(String className) {
return ClassUtils.isPresent(className, null);
}

private static class NonSecretsManagerPropertiesPlaceholdersResolver
implements PlaceholdersResolver {

private PlaceholdersResolver resolver;

NonSecretsManagerPropertiesPlaceholdersResolver(Environment environment) {
this.resolver = new PropertySourcesPlaceholdersResolver(environment);
}

@Override
public Object resolvePlaceholders(Object value) {
if (value.toString().contains("sm://")) {
return value;
} else {
return resolver.resolvePlaceholders(value);
}
}
}
}
Loading

0 comments on commit 67d994e

Please sign in to comment.