Hi @ada @richard.galvez ,
as a GCP IoT Core config management drop in replacement you could use the <application|service|device>_environment_variables. I’m wondering which limitations you see @ada, can you please share more insights?
A drop in solution (although without the versioning / rollback of a IoT core config) would be using a device_environment_variable and write a base64 encoded JSON object into it.
The consumer on the device just needs to decode base64 which should be a widely available package or library for most implementations.
You may use the balena-sdk or the balena-api to update
- a single device:
- API: Resources - Balena Documentation
- nodejs SDK: Balena Node.js SDK - Balena Documentation
- python SDK: Balena Python SDK - Balena Documentation
- a fleet service:
- API: Resources - Balena Documentation
- nodejs SDK: Balena Node.js SDK - Balena Documentation
- python SDK: Balena Python SDK - Balena Documentation
- or the whole fleet environment:
- API: Resources - Balena Documentation
- nodejs SDK: Balena Node.js SDK - Balena Documentation
- python SDK: Balena Python SDK - Balena Documentation
Please be aware, that using the same env var name will overwrite the content and the more specific content will win.
Please share your thoughts, we highly appreciate it!
Best regards
Harald