Well known config

[calvinrp]

• Added Warg client support for .well-known path, which required the warg_client::FileSystemClient::new_with_config() methods to be async;
• Support both warg login <registry-url> and warg login --registry <registry-url> (also for warg logout);
• Sets the default registry, without configuration, to be bytecodealliance.org; See discussions

Follow on work to respect HTTP cache headers.

[lann]

Should we call out that this is an advanced option and plain registry is preferred?

[calvinrp]

How do you mean "call out"?

I think either is OK. Just errors if you use both at the same time. Current look:

(base) > warg login -h
Manage auth tokens for interacting with a registry

Usage: warg login [OPTIONS] [URL]

Arguments:
  [URL]  The URL of the registry to use

Options:
      --registry <URL>                     The URL of the registry to use
      --config <CONFIG>                    The path to the client configuration file to use
      --ignore-federation-hints            Ignore federation hints
      --auto-accept-federation-hints       Auto accept federation hints
      --keyring-backend <KEYRING_BACKEND>  The backend to use for keyring access
  -h, --help                               Print help (see more with '--help')
  -V, --version                            Print version

[lann]

Maybe I'm just confused; what is the purpose of these two different arguments?

[calvinrp]

I was trying to support both warg login --registry <registry-url> (to not break existing instructions but also migrate to warg login <registry-url>.

Been trying, but clap doesn't really support it best I can tell with the derive args

[lann]

Ah OK; maybe pick one of the two to #[arg(hide)] and comment the reasoning?

[calvinrp]

Fixed, with hide