As part of the move to strict confinement for the openstackclients snap I’d like to allow the snap to access the standard location for the openstack clouds.yaml configuration file ($HOME/.config/openstack/clouds.yaml).
I’ve added a personal-files configuration for this access.
openstackclients is part of the suite of applications that is the clear owner of $HOME/.config/openstack. For consistency with other uses of personal-files, please update your snap.yaml to use dot-config-openstack as the interface reference, like so:
+1 to auto-connected access to $HOME/.config/openstack/clouds.yaml. However, @jdstrand given that this directory could also contain e.g. clouds-public.yaml, should we make the interface name file-specific?
@jamespage do you anticipate needing access to other files in that directory?
2 votes for, 0 against for use of and auto-connection for the personal-files interface for read-only access to $HOME/.config/openstack/clouds.yaml with the interface reference of dot-config-openstack-clouds-yaml. Granting. This is now live.
Note, while the snap declaration has been granted, there is a corresponding change to the review-tools that has been made that is not yet in production and new revisions will not pass automated review until it is. In the meantime, you can request manual reviews for new revisions and a reviewer can manually approve.