how to configure test resources with Flyway and R2DBC using different datasources?

[lucasgust]

as suggested in this discussion I'm using R2DBC as datasource default and JDBC/Flyway as migration to avoid transaction issues not being created within a reactive context.

now the problem is my integration tests because the test resources try to look for a migrate datasource inside r2dbc (and there is none).

PROJECT --> https://github.com/lucasgust/txwithr2dbc

I'm managed to implement a workaround but I'm feeling that's not the right way to do this.

flyway:
  datasources:
    migration:
      enabled: true

datasources:
  migration:
    db-type: mysql

r2dbc:
  datasources:
    migration:
      db-type: mysql
    default:
      db-type: mysql
      url: ${r2dbc.datasources.migration.url} --> need to reuse this url because test resources creates a new instance (different port) for each new datasource name
      username: ${r2dbc.datasources.migration.username}
      password: ${r2dbc.datasources.migration.password}

is there another way to achieve this?

[dstepanov]

I guess it's not possible with Test Resources. The only way is to have it named default. Please check this guide https://micronaut-projects.github.io/micronaut-r2dbc/1.0.x/guide/

[lucasgust]

@dstepanov thanks for your response. my workaround works but I thought there is an easier way...

[dstepanov]

What workaround is that?

[lucasgust]

this configuration I mentioned above, it's what I'm using in test environment:

r2dbc:
  datasources:
    migration:
      db-type: mysql
    default:
      db-type: mysql
      url: ${r2dbc.datasources.migration.url}
      username: ${r2dbc.datasources.migration.username}
      password: ${r2dbc.datasources.migration.password}