Multiple services domains per passport

[holocronweaver]

I want to use the same passport credentials across multiple service domains.

There are several ways I could think to accomplish this with git-passport. The easiest is to make the service field a delimited list of services. (I suggest comma-delimited since that is most common.) Alternatively, regex could be introduced. The latter could be useful for domains with multiple similar variations, though I haven't seen that much in the wild.

[frace]

That sounds like a good idea. I'll take this on my "consideration list".

[frace]

@holocronweaver Would you like to pull the "multidomain" branch and test if it gives suitable results? It allows a comma separated list (service = github.com, gitlab.com) of domains and checks if it matches a remote in a local .git/config.

See: https://github.com/frace/git-passport/commits/multidomain

[frace]

@holocronweaver
As an alternative solution I created another branch: https://github.com/frace/git-passport/commits/multidomainsection

This would let us do the following:

[passport "github, bitbucket, gitlab"]
email = ...
name = ...

[passport "github"]
email = ...
name = ...

which would eliminate possible issues with #29

[frace]

@Ferada I don't know if you are using the tool, yet. But which route would you consider to be nicer? Personally I tend to the branch multidomainsection since it has someting in common with the config style of .gitconfig.

[tverlaan]

@frace I think the naming of a passport should be something given by the user. Eg. work/private/fun/public. This would solve #29.
The URL's (or something that makes a string match) should be in the config. I'm not sure if service is correct naming. I'd probably go with url or url_matches. This could be a comma-separated list. I think this resembles the original .gitconfig the most.

Example:

[passport "private"]
email = user@example.com
name = U Ser
url = git.example.com

[passport "work"]
email = user@workexample.com
name = CEO U Ser
url = git.workexample.local,git.workexample.com

Even better would be a colon separated list, that would make it the same as fetch in .gitconfig. But then it needs proper quoting.

[frace]

@tverlaan

I think the naming of a passport should be something given by the user. Eg. work/private/fun/public.

Updated #29.
I think that'd be fine, too. However it needs to be mandatory to define an unique identifier always because configparser does not allow duplicate sections.

The URL's (or something that makes a string match) should be in the config.

Agreed.

I'm not sure if service is correct naming. I'd probably go with url or url_matches.

Yes, I used url in the early days of the script but switched to service instead because it's not an url what we use actually. What about providers or maybe hubs?

Even better would be a colon separated list, that would make it the same as fetch in .gitconfig. But then it needs proper quoting.

I'd be fine with a comma separated list, but this should allow colons if we'd omit e.g. the protocol http::

In [1]: mystr = "github:gitlab:bitbucket"

In [2]: print(mystr.split(":"))
['github', 'gitlab', 'bitbucket']

[frace]

@holocronweaver @tverlaan
If you don't have any further objections or ideas I will implement the requested features which will lead to a result allowing us to treat our configurations as shown below:

[passport "whateverUsersWantToPutHereUniquely"]
email = ...
name = ...
hubs = github:bitbucket:gitlab

[passport "whateverUsersWantToPutHereUniquely"]
email = ...
name = ...
hubs = github

[passport "whateverUsersWantToPutHereUniquely"]
email = ...
name = ...
hubs = gitlab

[passport "..."]
...