Changes to the configuration file have no effect

You enter a data source, a rule, or an assignment in appsettings*.json, restart the service—and nothing changes.

Service with an administration store (Gateway:Store:Path set).

If the store is new, the service takes over the operating data from the configuration file once. After that, the store decides. If operating data remains in the file, startup names it in a warning and doesn't use it. A store in which all data sources were later deleted doesn't take the entries back from the file.

1. Maintain data sources, rules, and assignments in the administration app or through /admin/v1/; see “Administrator guide for WKL Database Gateway Manager”.
2. Remove the operating data from the file so that the warning at startup disappears.
3. What concerns startup stays in the file: listening addresses, sign-in methods, service keys, limits, proxies, Gateway:Store.

Startup reports no warning about operating data in the file; the change in administration takes effect without a restart.

• Administration store and master key