Cory Johns

It looks like this is coming from `{'conjurefile': 'conf-file': [PosixPath('Conjurefile')]}`. We should probably exclude `conjurefile` entirely, and perhaps we should consider removing the JSON state serialization entirely in favor of...

The only reason I can think this might happen would be that sudo had cached auth at the start of the deployment that expired during the deployment. But I would...

Of course, the better fix would be to remove the requirement for entering the root password entirely, but that would require making `snap login` a pre-req.

The `h` key for help shouldn't be invoked if you're an input field, so I'll look into fixing that. There isn't a length limit for the password that I'm aware...

Ah, ok. I can reproduce that so I'll get a fix for that bit.

If this error is coming from Juju (or possibly even the provider), can we even do anything to support this in conjure-up?

Not entirely sure how conjure-up should handle this; if it can't reach the charm store, it can't deploy anything. Maybe we could do a check earlier in the process to...

+1 on not showing Units box for subordinates, but we should also figure out how many instances of the subordinates we expect so that we can have the Deploy Status...

Another use-case is we might want to check `snap whoami` to see if the user is logged in and thus won't require sudo to install the snap, so we can...

I'm not sure what's going on here, but the relevant bit from the field agent seems to be this: ``` Apr 29 04:15:01 juju-4222ff-4 kubelet.daemon[32157]: I0429 04:15:01.160018 32157 kubelet.go:1777] Starting...