Add the spring implementation for the placeholder-type parameter of the JDBC Driver to read dynamic properties in the Spring Boot configuration file

[linghengqian]

Feature Request

For English only, other languages will not be accepted.

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot make decision by current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Is your feature request related to a problem?

• FOR shardingsphere5.3 dynamic config suggestion #24498
• Encrypt queryWithCipherColumn not support Dynamic configuration In spring xml #22591

Describe the feature you would like.

• Add athe spring implementation for the JDBC Driver's placeholder-type parameter to read the YAML properties of application.properties or application.yml into ShardingSphere's configuration file. This seems like a natural thing to happen.
• We can actually only do unit testing on Spring Boot OSS 2.7, which has stopped being maintained, because I don't want to use Java API on Spring Boot OSS 3 on JDK8 through reflection.
• Consider the following jdbcURL.

jdbc:shardingsphere:classpath:config.yaml?placeholder-type=spring

• Assume that the following application.yml file exists in a typical Spring Boot project.

server:
  port: 8080

key:
    something:
        fixture-jdbc-url: jdbc:h2:mem:foo_ds_1;DB_CLOSE_DELAY=-1;DATABASE_TO_UPPER=false;MODE=MySQL
        fixture-username: sa

• Then for the intercepted fragment of the following YAML file config.yaml,

ds_1:
  dataSourceClassName: com.zaxxer.hikari.HikariDataSource
  driverClassName: $${key.something.fixture-driver-class-name::org.h2.Driver}
  jdbcUrl: $${key.something.fixture-jdbc-url::jdbc:h2:mem:foo_ds_do_not_use}
  username: $${key.something.fixture-username::}
  password: $${key.something.fixture-password::}

• This YAML snippet will be parsed as,

ds_1:
  dataSourceClassName: com.zaxxer.hikari.HikariDataSource
  driverClassName: org.h2.Driver
  jdbcUrl: jdbc:h2:mem:foo_ds_1;DB_CLOSE_DELAY=-1;DATABASE_TO_UPPER=false;MODE=MySQL
  username: sa
  password:

• Considering that Spring's dependencies are so huge, this is definitely an optional module.

[linghengqian]

• I'm working on this issue.

[linghengqian]

• This actually breaks the convention of Spring Boot. It is not reasonable to put the SPI implementation classes of ShardingSphere into the Spring container, because these classes are easily recreated by the context manager of ShardingSphere.