Petr Fedchenkov

> > Can we update publish workflow as well? > > Where do we use `actions/cache` in publish workflow? Ah, sorry, my mistake, I just remember your changes were about...

> LGTM, but I don't undestand the original code using the machine arch for all three fields. But that's a separate bug. Seems all commands we had previously in that...

> Note that the golangcilint complaints for the Run functions can be turned off by adding //nolint:gocyclo I am not sure, I can see that annotation [here](https://github.com/lf-edge/eve/pull/2855/files#diff-a954929a54118e77d88603fe5c903cadec3a1fa48a8e3e2e4a1385690fc00410R1380) (probably the link...

> I don't understand why you retain and use the BaseOsConfig golang type; the BaseOs type (which corresponds to the BaseOs protobuf message) should be sufficient here. We use config...

Well, I checked and seems we can get rid of uuidAndVersion in favor of contentTreeUUID. BTW, as we do not want to change API, seems Eden support should come first....

What do you think about including of BaseOsVersion? I still cannot understand the logic of hooking displayName of contentTree. Do you suggest me to modify API, wait for controller change...

> Once there is a ContentTreeStatus for the uuid you should be able to use the displayName from there. Do you need the displayName easier? I thought it is used...

I submitted a proposal: https://lists.lfedge.org/g/eve-tsc/message/913

Inside [ping](https://github.com/lf-edge/eve/blob/master/api/APIv1.md#ping) section you can find: `Valid credentials without authorization: 403`. Inside [authentication](https://github.com/lf-edge/eve/blob/master/api/APIv1.md#authentication) section: `The ping endpoint may be useful for a Device to check connectivity before registering. Since the...

But it needs to install scp inside EVE.