storj/cmd/storagenode-updater
Kaloyan Raev 958772467a cmd/storagenode-updater, pkg/process: Fix logging timestamp
After changing how we execute the storagenode-updater process we lost
timestamps in the log.

The fix is to start using zap logging.

The Windows Installer is changed to register the storagenode-updater
service in a way that the Windows Service Manager passes the
--log.output flag instead of the old --log.

The old --log flag is deprecated, but not removed. We will support it
for backward compatibility. This is required as the storagenode-updater
can auto-updated itself, but the Windows Service Manager of this old
installtion will continue passing the old --log flag when starting it.

Change-Id: I690dff27e01335e617aa314032ecbadc4ea8cbd5
Signed-off-by: Kaloyan Raev <kaloyan@storj.io>
2019-12-11 10:05:48 +00:00
..
testdata {internal/version,versioncontrol,cmd/storagenode-updater}: add rollout to storagenode updater (#3276) 2019-10-21 12:50:59 +02:00
main_test.go storagenode-updater: re-enable auto-update storagenode-updater (#3588) 2019-11-18 08:26:50 +01:00
main.go cmd/storagenode-updater, pkg/process: Fix logging timestamp 2019-12-11 10:05:48 +00:00
restart_mock.go cmd/storagenode-updater: make updater test windows compatible (#3542) 2019-11-14 16:03:49 +02:00
restart.go cmd/storagenode-updater: make updater test windows compatible (#3542) 2019-11-14 16:03:49 +02:00
windows.go cmd/storagenode-updater, pkg/process: Fix logging timestamp 2019-12-11 10:05:48 +00:00