Separate auth for the config

[ADRFranklin]

Right now you can only specify a single auth for running a repo, however this becomes a problem when you have the config file on one host and the repo on a different host.

Lets say you have the config file as a private repo on gitlab, but you want to access a private repo on github, well then you either have to have 2 configurations (which defeats the purpose of a single config file to manage it all).

A solution would be to have a config block which can take an auth type, or allow each repo to take multiple auth types, but then again it might not be easy to know which one is the one for the config, unless all where tried and only report the error if all fail.

[Southclaws]

Right now you can only specify a single auth for running a repo

A repository can only have a single authentication method, I don't see the need for multiple methods of authentication to a single repository. Whether that's the config repo or a target repo.

this becomes a problem when you have the config file on one host and the repo on a different host

I don't follow.

• What's "the config file" in the context of this question? Is it the configuration repository? The auth for this repository is configured via the configuration secret and there is only ever one of these.

• What's "the repo" too? A target repo? There can be multiple, and each one may have its own auth method defined via the A config function.