Have dev use ~/.netrc to store Github authentication instead of juggling raw passwords. [2/4] #237
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature migrates us away from doing our own password management
by embedding Github username/password authentication into our curl calls
and remote URL strings. Instead, we add entries for github.com and
api.github.com to the user's .netrc file, fix up all the direct curl
calls we make to ensure they know to look in .netrc for authorization info,
and rely on Git doing the same thing when it has to talk http.
The benefit to doing all this is that we no longer have to worry about
passwords that have special characters in them, nor do we spam auth info
all over the barclamps -- instead, it is in one place that all the tools
know how to access and that is a little more securable.