As noted by @sixcorners at
https://github.com/storj/storj/pull/3819#issuecomment-609025487, the
Windows installer code incorrectly fails if the ca.key file is not
present.
The ca.key file should not be necessary for regular storage node usage,
and in fact we recommend that users move the ca.key file to secure
storage rather than keeping it on the node.
I'm not sure how to run the tests, so I'll get a nod from the SNO Growth
team before merging.
Change-Id: Ib2fe236de5c75165644e880caa827a2a1a034c87
Co-authored-by: Stefan Benten <mail@stefan-benten.de>
On satellite, remove all references to free_bandwidth column in nodes table.
On storage node, remove references to AllocatedBandwidth and MinimumBandwidth and mark as deprecated.
Protobuf message, NodeCapacity, is left intact for backwards compatibility.
Once this is released to all satellites, we can drop the column from the DB.
Change-Id: I2ff6c6537fc9008a0c5588e951afea58ede85838
* First custom message
* Update text - change welcome dialog size
* dialogs workflow ok - config.yaml ko
* Delete on uninstall using custom action
* config file not deleted during upgrade
* remove useless registryvalue
* little fixes
* Fix back button in case of upgrade for verifyreadydlg
* same versions considered as upgrade
* same versions considered as upgrade
* Backup config file - does not work when changing install folder
* Installer version is taken from the version of storagenode.exe file
* registry read for retrieving install folder - parsing not working
* doesn't work
* Fix path extraction
* Separate install dir extraction from file movement
* Check the result of BackupConfigFile and RestoreConfigFile actions
* Set INSTALLFOLDER to the extracted path
