Declarative Configuration Support and DSL Integration

[ghost]

Description

Currently, configuring Jdbi involves some manual setup, which can be cumbersome and error-prone, especially in complex environments with multiple datasources and varying plugin requirements. To streamline this process, a declarative configuration approach that automatically configures the Jdbi setup within Quarkus could help to reach a common baseline:

• Configure Jdbi instances for each datasource entry automatically — reducing the need for manual bean configuration
• Create a DSL within Quarkus to define Jdbi configurations
• Expand DSL for plugins to be enabled for each Jdbi instance
• Incorporate support for configuring the SQL logger

In other words, the following class:

import jakarta.enterprise.inject.Produces;
import jakarta.inject.Inject;
import jakarta.inject.Singleton;
import org.jdbi.v3.core.Jdbi;
import org.jdbi.v3.core.statement.Slf4JSqlLogger;
import org.jdbi.v3.sqlobject.SqlObjectPlugin;

import javax.sql.DataSource;

public class PersistenceConfig {
  @Inject
  DataSource dataSource;

  @Produces
  @Singleton
  public Jdbi jdbi() {
    return Jdbi.create(dataSource).installPlugin(new SqlObjectPlugin()).setSqlLogger(new Slf4JSqlLogger());
  }
}

Could be automatically configured whenever a datasource configuration is enabled — with the exception of the plugins and the SQL logger.