Hello, my snap (https://snapcraft.io/lnav/) seems to require a review for the addition of the system-files interface to read the “/etc/lnav” directory. The directory is used to store configuration files that are common to all users on a machine. The configuration files are used to define how to parse log files. This request was raised by a user here – https://github.com/tstack/lnav/issues/1166
Since lnav is the clear owner of this path, it makes sense that the snap is able to read this configuration from the host if it already exists. +1 from me for use of and auto-connect of a system-files instance named etc-lnav for read access to /etc/lnav for the lnav snap.
Yes, +1 from me too. for the lnav snap to request read access (auto-connected) to /etc/lnav seems entirely reasonable. For awareness, this will be actioned at the end of the voting period as described here.