- Feb 20, 2018
-
-
Niko Ehrenfeuchter authored
After validating the config files we can now safely trigger the update if necessary. Refers to #18, #28
-
Niko Ehrenfeuchter authored
No checks are done in Update-Configuration any more, as the control logic has been changed to do those beforehand now. Therefore also Update-File is not comparing the write-times any more nor terminating the script if something fails (now returning $False instead). Refers to #18, #28
-
Niko Ehrenfeuchter authored
Instead of terminating the entire script immediately we log a message and pass on success / fail so the remaining script logic can deal with the situation. Refers to #18, #28
-
Niko Ehrenfeuchter authored
This adapts the updater to the new configuration locations (#18) and changes the control flow so that first the script will detect if any updates are necessary at all and then validate the configuration files (respecting what parts will be updated), preparing for the actual update tasks (as this is currently work-in-progress, those update tasks are disabled for now. Refers to #28
-
Niko Ehrenfeuchter authored
-
- Feb 19, 2018
-
-
Niko Ehrenfeuchter authored
The updater should also check if an existing configuration that won't be updated validates correctly with newer service binaries and stop the process of updating if the check fails. Refers to #28
-
Niko Ehrenfeuchter authored
Refers to #28
-
Niko Ehrenfeuchter authored
Refers to #18
-
Niko Ehrenfeuchter authored
Implements the core functionality of #28
-
Niko Ehrenfeuchter authored
This is required to correctly propagate exceptions from function calls. Otherwise every call has to specify the "-EA" flag explicitly. Refers to #28
-
Niko Ehrenfeuchter authored
-
Niko Ehrenfeuchter authored
Refers to #22
-
- Feb 18, 2018
-
-
Niko Ehrenfeuchter authored
Refers to #28, #13
-
Niko Ehrenfeuchter authored
Refers to #28, #18, #13
-
Niko Ehrenfeuchter authored
-
Niko Ehrenfeuchter authored
-
Niko Ehrenfeuchter authored
-
Niko Ehrenfeuchter authored
-
- Feb 16, 2018
-
-
Niko Ehrenfeuchter authored
Refers to #17
-
Niko Ehrenfeuchter authored
Refers to #18
-
Niko Ehrenfeuchter authored
-
Niko Ehrenfeuchter authored
-
Niko Ehrenfeuchter authored
Refers to #18
-
Niko Ehrenfeuchter authored
Refers to #18
-
Niko Ehrenfeuchter authored
Refers to #18
-
Niko Ehrenfeuchter authored
Refers to #18
-
- Feb 15, 2018
-
-
Niko Ehrenfeuchter authored
-
Niko Ehrenfeuchter authored
-
Niko Ehrenfeuchter authored
Refers to #18, #29
-
Niko Ehrenfeuchter authored
Refers to #18, #28, #29
-
Niko Ehrenfeuchter authored
There is no need to test a status file for correctness as the status class will simply create a new object with default values in case parsing an existing file fails. Refers to #22, #28
-
Niko Ehrenfeuchter authored
Refers to #18, #29
-
Niko Ehrenfeuchter authored
Refers to #29, #18, #28
-
Niko Ehrenfeuchter authored
Refers to #28
-
Niko Ehrenfeuchter authored
Refers to #28
-
Niko Ehrenfeuchter authored
Refers to #29
-
Niko Ehrenfeuchter authored
Refers to #28
-
Niko Ehrenfeuchter authored
Refers to #28
-
Niko Ehrenfeuchter authored
Refers to #28
-
Niko Ehrenfeuchter authored
Those objects are not meant to be instantiated directly but only using the Deserialize() methods which takes care of creating a new object in case deserializing fails for the status class.
-