Hey @wallyworld,
Apologize for the delay.
+1 from me for auto-connect ssh-public-keys to juju since its clearly required to add the user’s keys to authorized keys on created instances. +2 votes for, 0 votes against, granting auto-connect of ssh-public-keys to juju.
+1 from me as well for use-of and auto-connect of personal-files using the interface reference dot-local-share-juju for write access to $HOME/.local/share/juju as the juju snap is the clear owner of the directory. +2 votes for, 0 votes against, granting auto-connect of personal-files using the interface reference dot-local-share-juju for write access to $HOME/.local/share/juju.
+1 from me as well for use-of and auto-connect of personal-files using the interface reference dot-config-lxc for read access to $HOME/.config/lxc. +2 votes for, 0 votes against. Granting auto-connect of personal-files using the interface reference dot-config-lxc for read access to $HOME/.config/lxc to juju. This is now live. @wallyworld please note that in the snapcraft you shared you did not added the $HOME/.config/lxc directory to dot-config-lxc.
@wallyworld could you solve the issue with reading the $HOME/snap/lxd/current/.config/lxc/config.yaml?
I understand the usability issues with the several cloud config accesses but at this point this already got 2 votes against so I have granted the use but not auto-connect of the several personal-files read access requests: dot-aws, dot-azure, dot-google, dot-kubernetes, dot-maas, dot-oracle and dot-openstack.