Currently the mapper will write the inventory.json always to the cloud and with that overwrite the cloud values. Even without the JSON the name and type are always overwritten.

For technical properties that is ok, but properties like the name shouldn't overwrite cloud values.
If a cloud user changes the name after a restart of the tedge it will overwrite these values again.

There should be a way (at least a configuration option) the the mapper is not overwriting.
Maybe we can have two inventory.json. One carrying values that are written with every restart and one with values that are only written if the device does not exist yet.

That was just an idea, maybe there is a better solution