On Mon, 30 May 2011 10:40:00 +0200, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
So we need a way of storing tokens. The easiest thing to do would be to store a token for a (username, host) pair, so you'd run a command like:
IMHO that should be python-keyring. Let's not reinvent .netrc again.
Sure. I was talking design, not implementation :)
I guess the point I've argued myself to here is that I should implement this long form for now, and if a need arises add more conveniences (for example, reading from an environment variable or adding a command to set the defaults). Does anyone disagree too strongly with that?
Yeah. One more thing to think about though. Should lava-tool have per-command auth support (as in your examples above) or some side-band subcommands for auth that would be implicitly picked up by other commands (lava-tool auth ... && lava-tool submit-job ... VS lava-tool submit-job --auth-option ...)
I was thinking that there would be side-band commands such as auth-add, but I hadn't considered the point dreadfully hard.
Cheers, mwh