It feels a bit error prone to refresh before we even attempt to setup the device the first time, instead of establishing a common path which is always the one tested. We cannot avoid supporting the other path, in which the device first sets up and then refreshes, because that can always happen if the refresh doesnāt work for whatever reason (e.g. not fast enough to take precedence, or device is offline).
Not sure lazy classic registration plays a role here. If the device has a gadget, it has snaps in use and should attempt to refresh, so itās not lazy anymore, right? Or has that changed?
In either case, these questions are a hint that perhaps this is getting too complex for such a simple problem. Your suggestion 2 is also nice, and simpler. We might support a yaml configuration file in a well known place that is loaded when snapd is starting, assuming itās owned by root and with permission bits restrictive enough.
We might either do it at seed time only, or if we want to make it more generic we can request the file to be written in a location controlled by snapd, and we remove the file after the options are loaded, ensuring the authoritative place to remain inside snapd proper, which avoids user options from being overwritten if they are changed via the usual means.