The files themselves arenāt particularly controversial, but do you need read-only access or read/write? Why isnāt SNAP_USER_DATA/.config/glances good enough? Why do you need access to /etc/glances instead of SNAP_DATA/etc/glances (or similar)?
I donāt have a particular objection to read-only access to these directories, but write access means that your snap can write a non-snapās files and vice versa. How does glances handle different versions of config files (going forward and backward)?
Thanks, please report back when you hear something. Perhaps in the meantime readonly access is enough? You can then have your snap import the content into $SNAP_USER_DATA ($HOME within the context of your snap) and be on your way.
Note that I am implementing a review-tools check that will require that the interface reference be meaningful, but the snap in the store doesnāt yet use personal-files or system-files. I suggest for personal-files, using: