You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this falls somewhat outside the scope of this project, which primarily focuses on providing support for the AWS SDK. I guess the JDBC driver deserves a new Quarkiverse project by its own.
Thought, it appears to leverage the AWS SDK internally (at least for RDS, STS, and AUTH). STS, is already supported with GraalVM substitution. We do have an open call for contributions regarding RDS. And AUTH could be added as necessary.
This issue is a request to provide wrapper to Mysql & Postgres data sources to use the AWS JDBC Wrapper Driver.
Why?
The JDBC Wrapper driver provides additional support for connectivity to AWS Aurora hosted databases with features like:
Approach
I imagine this would be a case of adding an additional wrapper around the existing Postgres and MySQL.
We might then consume the uplifted driver like:
Postgres
implementation("io.quarkus", "quarkus-jdbc-postgresql")
implementation("io.quarkiverse.amazonservices", "quarkus-jdbc-postgresql-aurora")
MySQL
implementation("io.quarkus", "quarkus-jdbc-mysql")
implementation("io.quarkiverse.amazonservices", "quarkus-jdbc-mysql-aurora")
Plugin Parameters
A number of options are exposed using AWS JDBCDriver Parameters (normally injected into the data source on creation).
These could be exposed as properties to be configurable by the end consumer to enable/disable specific features and plugins
Other
The Hibernate ORM documentation warns against defining a custom ORM datasource as it is likely to fail the GraalVM build.
I am not super confident in my graalvm knowledge, but do believe this would be useful for the community.
The text was updated successfully, but these errors were encountered: