Thanks for the info. This seems like a hole? Let me explain further my use case, maybe Im using balena incorrectly.
It seems like for at least some subset of config.txt flags these are very application and hardware specific and should change with the application. If Im adding an i2c device, I need to know that i2c has been enabled or at least very strongly indicate it needs to be enabled for this application to work.
Id also like to automated deploy to the cloud presumably via a ci tag, Who and when do we remember to read the comments and swap out all the config variables in the cloud service? Never mind with 10 or 100 devices in the fleet, now Im juggling old and new configuration vars as those devices slowly update?
Im also worried about being able PRs locally on device before going to the cloud. There seems to be no way to consistently know that the vars were applied correctly without relying on humans to edit files outside of the commit which we know wont work.
Does anyones workflow solve this someway Im not thinking of?