Support using environment variables to configure username and passwords #1961
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.
Pull Request Check List
This is just a reminder about the most common mistakes. Please make sure that you tick all appropriate boxes. But please read our contribution guide at least once, it will save you unnecessary review cycles!
As per #1871 you cannot configure HTTP basic auth using environment variables. This is a problem for a lot of use cases:
Docker - using build time secrets means you can inject the HTTP basic auth configuration as an environment and download packages from a private repository without including this information in the resulting container. That's harder to do if you execute
poetry config ...
.User onboarding - many companies inject credentials into laptops as environment variables, and tools should be configured to work with those with a minimum of configuration. Simply having
POETRY_HTTP_BASIC_MY_INTERNAL_PYPI_USERNAME
andPOETRY_HTTP_BASIC_MY_INTERNAL_PYPI_PASSWORD
should be sufficient.