xs996 opened a new issue, #30896: URL: https://github.com/apache/shardingsphere/issues/30896
## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? ShardingSphere-5.4.1 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-JDBC ### Expected behavior The database password is parsed successfully using placeholder $${FIXTURE_PASSWORD::} ### Actual behavior Database password parsing failed using placeholder ### Reason analyze (If you can) ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. ### Example codes for reproduce this issue (such as a github link).  According to the official documentation, I want to use a placeholder to replace my database password. When I try to do this, I fail. Where the data source is built, the placeholder information is read：  So I tried to modify the init of JDBCRepository and the build method of NewStandaloneContextManagerBuilder. By modifying the source code and testing, I successfully replaced my password with a placeholder, but the startup still reported an error.  If I want to continue to modify the source code, besides replacing my password in build and init, do I need to modify anything else? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
