Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bad follower token: netrc missing "password"? #23

Open
mherold opened this issue May 27, 2021 · 2 comments
Open

bad follower token: netrc missing "password"? #23

mherold opened this issue May 27, 2021 · 2 comments

Comments

@mherold
Copy link
Contributor

mherold commented May 27, 2021

According to e.g. https://www.gnu.org/software/inetutils/manual/html_node/The-_002enetrc-file.html, I gather the format of netrc should be:

"default login #{username} password #{password}\n" instead of

File.write netrc_path, "default login #{username} #{password}\n"

I had errors complaining about a "bad follower token". For my use case, I overwrote the generated netrc with the following, which fixed the problem:

machine github.com login XXX password YYY
default login anonymous password user@site
@troykinsella
Copy link
Owner

Yeah I'm thinking one should just be able to supply the contents of the netrc file, fully. Aside from being incorrect, the above template is too restrictive to be useful.

@mherold
Copy link
Contributor Author

mherold commented May 28, 2021

Yes that might be useful. I mean, the current configuration is nice & easy and may cover the majority of people's use cases. On the other hand, in our use case we have multiple roles from different private repositories in our requirements.yml. If different credentials are required for each I think this is currently not possible without some workarounds / "manual" changes. Out-of-the-box I only see these possibilities:

(A) Using git username/password: Only one username/password combination can be configured (=> netrc)

(B) Using git ssh keys: Only one key can be configured (but: e.g. if you want to use github deploy keys and have multiple repos, you would need to configure multiple keys).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants