Hello Mender community,
We came across this issue today and it would be interesting to hear your thoughts about it. Let’s consider the following scenario:
After a Mender-enabled device is shipped to customers, the development team implements a new feature that requires a new path to exist in
When the customer OTA updates their device (using a
.mender package behind the scenes) they don’t get their
/data partition changed as
.mender files do not contain a
/data partition. This results in unexpected behavior and developers get sad because “it worked on their bench”.
Is there a Menderic (a la pythonic) way to do this? The solution we’ve come up thus far involve an one-time script that “fixes” the
/data partition (e.g. by creating the missing paths/files) but we’d rather avoid this if we can.