at the moment, there is info for a unikernel which returns the unikernel configuration without the unikernel image itself. and there is get that returns the entire configuration (including image).
in the light of reproducible builds etc. it'd be great to get the uniquely identified sha-256 hash of the running (and uncompressed) binary of a unikernel. this would ease inventory management. the hash could be computed upon unikernel startup (from the uncompressed data dumped to disk) to avoid re-computing the hash on every request.
I'd appreciate it being part of the info subcommand (meaning revising the Unikernel.config record and ASN grammar -- but note that it should not be provided by albatrossclient*, but instead computed by the server! so eventually the get and info subcommands should use some other data structure than the create/force-create subcommands)
at the moment, there is
infofor a unikernel which returns the unikernel configuration without the unikernel image itself. and there isgetthat returns the entire configuration (including image).in the light of reproducible builds etc. it'd be great to get the uniquely identified sha-256 hash of the running (and uncompressed) binary of a unikernel. this would ease inventory management. the hash could be computed upon unikernel startup (from the uncompressed data dumped to disk) to avoid re-computing the hash on every request.
I'd appreciate it being part of the
infosubcommand (meaning revising the Unikernel.config record and ASN grammar -- but note that it should not be provided by albatrossclient*, but instead computed by the server! so eventually thegetandinfosubcommands should use some other data structure than the create/force-create subcommands)