Command snappy-remote should support --allow-unauthenticated from snappy install

[Caio Begotti]

Right now when you are developing a .snap and Snappy fails with "signature verification failed with exit status 10" you end up without a way to install and test your package.

Ideally snappy-remote should support passing options to the install command it runs, at least --allow-unauthenticated should be supported so developers and testers can bypass this error.

[Caio Begotti (caio1982)]

Btw, I get that it does not happen in developer mode but otherwise snappy-remote would not be really useful in non-devel cases then?

[Nick McCloud (nick-xrv)]

Semi-workround: Whilst it fails to install correctly, snappy-remote does at least provide a way of getting files on to the target which you can then launch manually. This works for the hello-world and my own Python app.

[Daniel Holbach (dholbach)]

We should document this on https://developer.ubuntu.com/en/snappy/tutorials/build-snaps/ too.

Does --allow-unauthenticated get passed to snappy?

[Daniel Holbach (dholbach)]

Is this still a problem?

[Paul Larson (pwlars)]

I think this should no longer be a problem, snappy-remote does --allow-unauthenticated by default

[Leo Arias (elopio)]

Marking as invalid for now. The docs no longer have instructions to install the snaps. We need snappy try and something like snappy remote install, and document them.