Auto deployer for new releases

[mfdlabs-ops]

So currently we have someone manually deploy files to the nodes.

We are thinking of writing dedicated software that automates this (only for machines not hooked onto our network, else we can just use ARCBD)

The app will poll this repositories releases and determine if there's a new version by reading registry key. By default it will not deploy releases marked as "pre-release", unless we put a very specifc string into the release title that overrides this (do not do this, only do this on very specific cases as it will deploy to every available node)

To do this we may also need to create a bridge tcp or udp server on the bot that can accept maintenance commands from an external source, this is so we can enable maintenance automatically before deployment. This will also kill every arbitered instance so we have enough memory to complete the deploy.

When it finds a new release, it will download the release and decompress it into the predefined path that is in it's configuration (check vault), in there it will Set-Location to the predefined path, and run the unpacker script, and then Set-Location into the newly created folder. If the settings say, it will copy the configuration files from the previous deployment and overwrite the new deployment's configuration files.

Finally it will run a script that:

1. Kills all arbitered instances (if not killed already)
2. Kills the currently running bot
3. Goes into the new directory and starts the ps1 script RunService.ps1

It will then persist this version in the registry.

This auto deployer will have timespan setting that determines the polling interval.

WARNING: If we can somehow get a webhook for this that listens for changes instead of polling, do that instead.