DataSourceBuilder throws an UnsupportedDataSourcePropertyException when trying to derive a DataSource from an unknown DataSource type

[ghost]

In our application (Spring Boot 2.5.2) we are trying to use com.amazonaws.xray.sql.TracingDataSource as the primary DataSource; it's essentially a wrapper around a regular data source to enable AWS X-Ray metrics.
During startup, the application tries to create a derived DataSource from it (DataSourceBuilder.derivedFrom(dataSource), the Liquibase starter is doing this).
The TracingDataSource is not recognized as a source for MappedDataSourceProperties, so we end up with a ReflectionDataSourceProperties, trying to to find the getters for the properties by reflection. However, it is erroneously looking for getter methods with one String parameter (DataSourceProperty:293-294). Even if such getters were to exist, they are later on (ReflectionDataSourceProperties:553) called with no parameters, resulting in an IllegalArgumentException anyway.

Example configuration to trigger the issue:

  @Bean(name = "dataSource")
  @Primary
  public DataSource tracingDataSource(HikariDataSource dataSource) {
    return new TracingDataSource(dataSource) {
      public String getUrl() {
        return ((HikariDataSource) delegate).getJdbcUrl();
      }
      ...
    };
  }

  @Bean
  public HikariDataSource hikariDataSource(DataSourceProperties properties) {
    HikariDataSource dataSource =
        properties.initializeDataSourceBuilder().type(HikariDataSource.class).build();
    if (StringUtils.hasText(properties.getName())) {
      dataSource.setPoolName(properties.getName());
    }
    return dataSource;
  }

  @Bean
  public DataSource derived(@Qualifier("dataSource") DataSource dataSource) {
    DataSourceBuilder<?> builder =
        DataSourceBuilder.derivedFrom(dataSource).type(SimpleDriverDataSource.class);
    return builder.build(); // UnsupportedDataSourcePropertyException: Unable to find suitable method for url
  }

[wilkinsona]

Thanks for the report, @migueldiogo-cycleon. While you're waiting for a fix, I think you could work around the problem by using @LiquibaseDataSource on a @Bean method that defines the Liquibase-specific DataSource rather than setting spring.liquibase.user and .password.

[ghost]

@wilkinsona thanks for the workaround! I managed to get things working with the @LiquibaseDataSource annotation as you suggested.
If I can be of further assistance in solving this issue, please let me know.

[wilkinsona]

Closing in favor of #27453.