datasource-settings.properties file is loaded by codes, through file name only.
But the better things for application.yml are two 1. It could be overrided by system env, which is much more friendly than config file change. 2. In our container definition, application yaml file could be change through system env, not just values of config items, but including provider names. You could read skywalking-docker about this. This file should be merged into application.yaml, and it is open to change. Please submit pull request if you want. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. ------------------ Original ------------------ From: Juan Pan <[email protected]> Date: Fri,Sep 27,2019 7:14 PM To: dev <[email protected]> Subject: Re: Why is `datasource-settings.properties` necessary when storage is `MySQL` Hi everyone, I am exploring SkyWalking, and i find when storage is`MySQL, `datasource-settings.properties` is needed to set properties, while all the properties of H2 storage can be set through `application.yml`. Why is `datasource-settings.properties` necessary for MySQL storage? Do they have different loading mechanism?? Thanks for your help. :) Regards, Trista Juan Pan [email protected] Juan Pan(Trista), Apache ShardingSphere
