Hey @snicoll — quick question about configuring two datasources.

In the Spring Boot docs for the two-datasource setup, the second datasource ends up using a different prefix/property namespace (e.g., app.datasource) rather than being a named datasource under spring.datasource:
link to doc

By analogy, OAuth client registrations are named and grouped under a single prefix (e.g., azure, snow) instead of requiring a totally different top-level prefix:

spring:
  security:
    oauth2:
      client:
        registration:
          azure: ...
          snow: ...

Would it make sense to support something similar for multiple datasources, e.g. named entries under spring.datasource:

spring:
  datasource:
    first:
      url: jdbc:mysql://localhost/first
      username: dbuser
      password: dbpass
      configuration:
        maximum-pool-size: 30
    second:
      url: jdbc:mysql://localhost/second
      username: dbuser
      password: dbpass
      max-total: 30

…instead of requiring a separate top-level prefix for the second datasource:

spring:
  datasource:
    url: jdbc:mysql://localhost/first
    username: dbuser
    password: dbpass
    configuration:
      maximum-pool-size: 30
app:
  datasource:
    url: jdbc:mysql://localhost/second
    username: dbuser
    password: dbpass
    max-total: 30

Curious if this is intentionally out of scope (e.g., binding/auto-config constraints), or if it’s something Boot would consider supporting/documenting.

Configuring Two DataSources How-To code sample is inconsistent #48448

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions