And its .bak file. Those are checkpointed protobuf files which
have their chains verified before writing them, but also when they
are read after a reboot. When we load from
/persist/checkpoint/controllercerts we also publish ControllerCerts for
use by others.
This will remove the need to for /persist/certs/server-signing-cert.pem

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit d28f531)

Instead it is only kept in memory/pubsub and lookupControllerSigningCert
can be used to fetch it.

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit 8b4c427)

The need for Touch went away when we started accepting arbitrarily old
checkpoints.

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit 7fd77c7)

And make sure we update the checkpoint when there are real
changes to the controller certs. This requires comparing the
set of Keys aka hashes of the certificates to avoid a falsely
detection changes due to ordering differences in the protobuf
bytes.

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit ae9bc23)

They are created from the checkpointed controllercerts and lastconfig
when zedagent starts, and then they are published to other agents.

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit 00480f4)

The ConfigItemValueMap will no longer be a persistent publications
hence there will be no need to convert from old to new formats,
nor set default values. The defaults will be applied by zedagent
on startup.

A follow-on commit adds back the handling of /config/GlobalConfig/global.json
in zedagent.

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit c2b3a53)

Zedagent initializes it from /persist/checkpoint/lastconfig
on startup so that other agents can get their global config.

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit ace2402)

Since some persistent publication are no longer persistent

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit 8747315)

And remove some use of file access in favor of pubsub calls.

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit 9089e09)

But do this in zedagent similar to how it handles bootstrap config
(the old code was in upgradeconverter).

A follow-up commit removes the use of /persist/ingested and related
sha256 comparisons.

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit ffe87b5)

This no longer makes sense since we ingest into memory and not into
files in /persist. Only the DevicePortConfig gets ingested by nim
into a persistent publication and that can handle multiple ingestions
without indigestion.

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit 0088d2a)

If we have a /persist/checkpoint/lastconfig we ignore
re-reading those files. They will have been taken into account
in forming /persist/status/nim/DevicePortConfigList/

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit a7789a4)

Have client wait for a checkpoint even if the device is already onboarded.

Signed-off-by: eriknordmark <erik@zededa.com>
(cherry picked from commit 0d4aaf0)