ppa-dev-tools.ppa tests always asks for auth

Yes, Lucas ran into this same issue with the snap. I think he ended up using the package from the ppa-dev-tools PPA since it won't have this problem.

Thanks for reporting this; I mostly dogfood from git so didn't notice it when testing the snap.

I'm marking this bug as 'bitesize' as it looks like an issue that is easy to fix and suitable for newcomers in Ubuntu development. If you need any help with fixing it, talk to me about it.

I tested one of the ubuntu-dev-tools scripts run in an LXC environment and found it has the same problem. So I'm not sure this is specific to snap, and may be something in launchpadlib rather than in the client itself. I don't rule out that there may be a way to work around it by manually doing the Credentials handling that launchpadlib's login_with() should be doing.

I've implemented the solution described in comment #4, and this is now available in the 0.5 release.

Essentially, on a properly logged in system you can run `ppa credentials`, which writes out a credentials.oauth file. Copy that to your target system where you want to run ppa-dev-tools, then do `ppa --credentials ./credentials.oauth <command> ...`

There may well be additional polish required to make the snap work more seamlessly, so definitely reopen this if the solution does not feel complete yet.

It would be interesting to be able specify where to store the credential file. Right now it's possible to pass an argument after "ppa credentials" and it will fail with "Error: Invalid ppa name '{args.ppa_name}'". Another way to address this would be to forbid that extra argument.