We envisage our devices being flashed to a ‘landing’ application. From here we are intending to do some provisioning checks, and also potentially negotiation for credentials such as certificates (i.e. obtaining an AWS IoT Core certificate).
The eventual application that is intended for the device may vary, but the means for cloud communication (i.e. via these obtained credentials) is consistent. We intend to switch the device to a specific application, but would like to do some of these preliminary steps before then such that the application can have certificates in place when starting.
I have noted from documentation :
Warning: For devices running balenaOS version 2.12.0 and above, data in persistent storage (named volumes) is automatically purged when a device is moved to a new application.
Is there a way for storing data that survives beyond a device being moved to a new application?
We’d like to have shared files such as a certificate from a named volume, setup in one application, to a different container started in a switched to application.