Swastyy commented on pull request #11425: URL: https://github.com/apache/shardingsphere/pull/11425#issuecomment-884297056
> > > > Hi @Swastyy > > > > Thanks for your hard work! > > > > I think there may be some misunderstandings. ShargingSphere-Proxy has a configuration file `server.yaml`, which is not exist in `ShardingSphere-JDBC`. > > > > The configuration in `server.yaml` changes in different versions, so this record of change history is needed. > > > > For example: > > > > the structure of authority configuratio has changed by #10297, you can refer to the git history of the file [server.yaml](https://github.com/apache/shardingsphere/blob/master/shardingsphere-proxy/shardingsphere-proxy-bootstrap/src/main/resources/conf/server.yaml) . > > > > > > > > > Hey, I have a doubt like changement of authority configuration is not what we want right? We want to store the changes of `server.yaml` so putting the users sections inside the authority in `server.yaml` file is not we will do. I mean we won't make any change in the above file right? > > > > > > I'm sorry I didn't understand what you mean. What we need to do now is to add a change history, so have you read the git history? This file has indeed been updated many times, with new and changed parameters. > > Git history is in file itself? > [Here](https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-jdbc/configuration/yaml/change-history/) is an example of ShardingSphere-JDBC. > > For `server.yaml`, we only need to list the differences between several major versions of `server.yaml`. > Like 5.0.0, 4.x, 3.x, 2.x. Ohhk I get it. Thank you so much. -- 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]
