Add flyway-database-postgresql for grails-forge-analytics-postgres native deploy

[jamesfredley]

Summary

After PR #15647 unblocked dockerBuildNative for grails-forge-analytics-postgres and the resulting native binary built and pushed cleanly, the Cloud Run revision still failed its startup probe (run 25578314349 / run 25578315293):

ERROR: (gcloud.run.deploy) The user-provided container failed to start and listen on the port
defined provided by the PORT=8080 environment variable within the allocated timeout.

That makes 8.0.x's Deploy to Google Cloud Run (the web-netty one) green again, but Deploy analytics to Google Cloud Run red - this is the third-and-final blocker on the broken Forge deploy pipeline.

Root cause

Reproducing the analytics native binary locally on Docker against a postgres:15.3 sidecar showed it crashing during datasource initialization, well before binding to :8080:

HikariPool-1 - Start completed.
Running migrations for database with qualifier [default]
ERROR io.micronaut.runtime.Micronaut - Error starting Micronaut server:
  Bean definition [javax.sql.DataSource] could not be loaded:
  Unsupported Database: PostgreSQL 15.3
Caused by: org.flywaydb.core.api.FlywayException: Unsupported Database: PostgreSQL 15.3
    at org.flywaydb.core.internal.database.DatabaseTypeRegister
        .getDatabaseTypeForConnection(DatabaseTypeRegister.java:131)

Flyway 10.x split the per-database DatabaseType SPI implementations out of flyway-core into dedicated modules. After the May-2026 adoption of micronaut-platform (commit b406076e87) pinned us to flyway-core:10.22.0, the analytics service no longer had a PostgreSQL DatabaseType on the runtime classpath, so Flyway's ServiceLoader<org.flywaydb.core.internal.database.DatabaseType> returned an empty match for the postgres connection, threw Unsupported Database, and the Micronaut bootstrap aborted before the HTTP server could bind.

Previously this was masked by the earlier dockerBuildNative failures - the build never produced an image to deploy, so we never saw the runtime error.

Fix

Add runtimeOnly 'org.flywaydb:flyway-database-postgresql' to grails-forge-analytics-postgres/build.gradle. micronaut-flyway-bom:7.9.2 already manages the matching org.flywaydb:flyway-database-postgresql:10.22.0 artifact, so no explicit version pin is needed:

+--- io.micronaut.flyway:micronaut-flyway-bom:7.9.2
|    +--- org.flywaydb:flyway-database-postgresql:10.22.0 (c)
|    +--- io.micronaut.flyway:micronaut-flyway:7.9.2 (c)
|    \--- org.flywaydb:flyway-core:10.22.0 (c)

Verification

Local repro on Docker 29.3.0 (post-fix image rebuilt with the same 21.0.2-ol9 GraalVM Community native-image container the deploy workflows use):

$ docker run -d --name analytics-pg -p 15432:5432 -e POSTGRES_USER=dbuser \
    -e POSTGRES_PASSWORD=theSecretPassword -e POSTGRES_DB=postgres postgres:15.3
$ docker run -d --name analytics-app -p 18082:8080 \
    --add-host=host.docker.internal:host-gateway \
    -e MICRONAUT_SERVER_PORT=8080 \
    -e DATASOURCES_DEFAULT_URL=jdbc:postgresql://host.docker.internal:15432/postgres \
    -e DATASOURCES_DEFAULT_USERNAME=dbuser \
    -e DATASOURCES_DEFAULT_PASSWORD=theSecretPassword \
    grails-forge-local:analytics

HikariPool-1 - Start completed.
Flyway - Database: jdbc:postgresql://...:5432/postgres (PostgreSQL 15.3)
Flyway - Creating Schema History table "public"."flyway_schema_history" ...
Flyway - Schema "public" is up to date. No migration necessary.
io.micronaut.runtime.Micronaut - Startup completed in 193ms.
  Server Running: http://...:8080

Native binary now binds to :8080 within the Cloud Run startup-probe window. The Cloud Run-side service config (Cloud SQL connection name, secrets, env vars) is unchanged from prior successful deploys (most recent: 2026-04-16 run 24524756128).

[Copilot]

Pull request overview

This pull request fixes native startup failures of the grails-forge-analytics-postgres Cloud Run deployment by ensuring Flyway can recognize PostgreSQL at runtime when using Flyway 10.x (where database support is split into per-database modules).

Changes:

• Add the PostgreSQL Flyway database module (org.flywaydb:flyway-database-postgresql) to the runtime classpath.
• Rely on BOM-managed versions for the PostgreSQL JDBC driver and Logback runtime dependency (removing explicit version usage in this module).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[testlens-app]

🚨 TestLens detected 2 failed tests 🚨

Here is what you can do:

1. Inspect the test failures carefully.
2. If you are convinced that some of the tests are flaky, you can mute them below.
3. Finally, trigger a rerun by checking the rerun checkbox.

Test Summary

Check	Project/Task	Test	Runs
CI - Groovy Joint Validation Build / build_grails	:grails-data-hibernate5-dbmigration:test	GroovyChangeLogSpec > outputs a warning message by calling the warn method	❌
CI - Groovy Joint Validation Build / build_grails	:grails-data-hibernate5-dbmigration:test	GroovyChangeLogSpec > updates a database with Groovy Change	❌

🏷️ Commit: ca11e8f
▶️ Tests: 8303 executed
🟡 Checks: 14/35 completed

Test Failures

GroovyChangeLogSpec > outputs a warning message by calling the warn method (:grails-data-hibernate5-dbmigration:test in CI - Groovy Joint Validation Build / build_grails)

Condition not satisfied:

output.toString().contains('warn message')
|      |          |
|      |          false
|      21:22:04.291 [Test worker] INFO org.hibernate.dialect.Dialect -- HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
|      Running Changeset: changelog.groovy::2::John Smith
|       
|      UPDATE SUMMARY
|      Run:                          1
|      Previously run:               0
|      Filtered out:                 0
|      -------------------------------
|      Total change sets:            1
|       
|      Liquibase: Update has been successful. Rows affected: 1
21:22:04.291 [Test worker] INFO org.hibernate.dialect.Dialect -- HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
Running Changeset: changelog.groovy::2::John Smith
 
UPDATE SUMMARY
Run:                          1
Previously run:               0
Filtered out:                 0
-------------------------------
Total change sets:            1
 
Liquibase: Update has been successful. Rows affected: 1

	at org.grails.plugins.databasemigration.liquibase.GroovyChangeLogSpec.outputs a warning message by calling the warn method(GroovyChangeLogSpec.groovy:87)

GroovyChangeLogSpec > updates a database with Groovy Change (:grails-data-hibernate5-dbmigration:test in CI - Groovy Joint Validation Build / build_grails)

Condition not satisfied:

output.toString().contains('confirmation message')
|      |          |
|      |          false
|      21:22:03.855 [Test worker] INFO org.hibernate.dialect.Dialect -- HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
|      Running Changeset: changelog.groovy::1::John Smith
|       
|      UPDATE SUMMARY
|      Run:                          1
|      Previously run:               0
|      Filtered out:                 0
|      -------------------------------
|      Total change sets:            1
|       
|      Liquibase: Update has been successful. Rows affected: 1
21:22:03.855 [Test worker] INFO org.hibernate.dialect.Dialect -- HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
Running Changeset: changelog.groovy::1::John Smith
 
UPDATE SUMMARY
Run:                          1
Previously run:               0
Filtered out:                 0
-------------------------------
Total change sets:            1
 
Liquibase: Update has been successful. Rows affected: 1

	at org.grails.plugins.databasemigration.liquibase.GroovyChangeLogSpec.updates a database with Groovy Change(GroovyChangeLogSpec.groovy:61)

Muted Tests

Note

Checks are currently running using the configuration below.

Select tests to mute in this pull request:

🔲 GroovyChangeLogSpec > outputs a warning message by calling the warn method
🔲 GroovyChangeLogSpec > updates a database with Groovy Change

Reuse successful test results:

🔲 ♻️ Only rerun the tests that failed or were muted before

Click the checkbox to trigger a rerun:

🔲 Rerun jobs

---

Learn more about TestLens at testlens.app.