I propose we add a new yaml key under “content” that allows to specify “auto-refresh: true” as an opt-in. If snapd finds content with this option it will copy those files from the gadget snap to the target filesystem if the files are different.

well, depends with regard to that specific bug … on a pi install you might manually modify things like config.txt or cmdline.txt for specific system related bits (fixed HDMI resolution etc), blindly overwriting such files seems like a bad idea in that case.

we could allow a file blacklist “never-touch: […]”

add a checksum test, update only if the file is original (but then we should notify the user)

or we actually parse the file and carry changes over

in general it seems like a good plan for all bootloader binaries though.