Implement version check mechanism between daemon and stack

[umgefahren]

We should implement a version check mechanism between the daemon and the stack. It's not good that there isn't one

[Zollerboy1]

Should this check for exact version matches or can we be less strict? I guess, in the same vein, we should also introduce version checks for all communication over grpc (i.e. between stack and script, as well as soon between stack and cli)?

[umgefahren]

Should this check for exact version matches or can we be less strict?

Let's just use SemVer and issue a warning if we are a aware of another version that exists and we could update too.

I guess, in the same vein, we should also introduce version checks for all communication over grpc (i.e. between stack and script, as well as soon between stack and cli)?

Yes and the SDKs too (maybe).

@Lxixnxuxs just pinging you here because you are working on the CLI.

[Zollerboy1]

Let's just use SemVer and issue a warning if we are a aware of another version that exists and we could update too.

I don't understand this. Can you elaborate?

[umgefahren]

The components have a semver conformant version. A dependency (i.e. hyvectl depends on hyved) specifies a minimum required version (as standard to semver) and will throw an error or warning on a version mismatch. We can also hardcode the newest version of the dependency we are aware of (at build time) so we can drop hints that a restart or update might be available.