Juju and snappy implementation spike - feedback please

[Stuart Bishop]

On 9 August 2016 at 19:08, Ian Booth <ian.booth at canonical.com> wrote:

> I personally like the idea that the snap could use a juju-home interface to
> allow access to the standard ~/.local/share/juju directory; thus allowing
> a snap
> and regular Juju to be used interchangeably (at least initially). This will
> allow thw use case "hey, try my juju snap and you can use your existing
> settings" But, isn't it verboten for snaps to access dot directories in
> user
> home in any way, regardless of what any interface says? We could provide an
> import tool to copy from ~/.local/share/juju to ~/snap/blah...
>
> But in the other case, using a personal snap and sharing settings with the
> official Juju snap - do we know what the official snappy story is around
> this
> scenario? I can't imagine this is the first time it's come up?
>


The big difference to me is that $SNAP_USER_DATA will roll back if the snap
is rolled back. I'm not sure what happens if the snap is removed and
reinstalled. Given end users should no longer need to be messing around
with the dotfiles, I think the rollback behaviour is what should drive your
decision. Is it nice behaviour? Or will it mess things up because rollback
will cause things to get out of sync with the deployments?


-- 
Stuart Bishop <stuart.bishop at canonical.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20160809/4e0f2e8f/attachment.html>