You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When application update, current appsettings.yaml file from current install directory overrides by new file from the installer.
This behaviour leads to overwrite all settings that was set previously.
Expected behavior
When application update, we should add missing configuration keys, but not overwrite already placed config keys.
Or make other migration behaviour that will be able to migrate config files more flexible while update.
Reproduction steps
Install previous release
Change appsettings.yaml file
Update application to latest release using installer
appsettings.yaml file became overwritten
Version: 1.0.2
The text was updated successfully, but these errors were encountered:
Also, on macOS system - appsettings.yaml is a part of SSC.app bundle.
Apple recommends to not modify bundle files in runtime, so we should think about not store application settings into bundle itself on macOS
Current version of SSC is not overriding appsettings.yaml file when install on Windows and Linux.
But for macOS it is still should be placed directly into Bundle. It is not much pain due to not so often usage on macOS systems as server-side, but it definitely will be problem in future.
🐛 Bug Report
When application update, current
appsettings.yaml
file from current install directory overrides by new file from the installer.This behaviour leads to overwrite all settings that was set previously.
Expected behavior
When application update, we should add missing configuration keys, but not overwrite already placed config keys.
Or make other migration behaviour that will be able to migrate config files more flexible while update.
Reproduction steps
appsettings.yaml
fileappsettings.yaml
file became overwrittenVersion: 1.0.2
The text was updated successfully, but these errors were encountered: