You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to copy a repo via HTTPS where an authentication to the repository is required fails.
The error message:
Error: Execution of 'git clone --branch Preview https://xxxxxx/xxxxxxx/_git/xxx /var/www/' returned 128: Cloning into '/var/www/'...
fatal: could not read Username for 'https://xxxxxx': No such device or address
Expected Behavior
Define base_auth_(username|password) and git should be able to fetch the repository.
Steps to Reproduce
Steps to reproduce the behavior:
Try to load a git repository over an HTTPS, that is protected via user authentication.
Provide both base_auth_(username|password).
Get the error.
Environment
vcsrepo 5.2.0
Puppet 7.18.0
Debian 11
Azure Devops Server (in a git environment)
Additional Context
Similar to git http password not allowed #97, but couldn't be resolved by providing a .netrc file to the user set via the "user" variable.
Providing username and password by adding them in the https://username:[email protected] syntax does not solve the issue.
The text was updated successfully, but these errors were encountered:
This works for vcsrepo within the source parameter.
Note that these credentials will then be stored within the configuration of that repo working copy, viewable by anyone with read access, and re-usable by any other git operations, external to vcsrepo, within that working copy. This could be desirable or undesirable, depending on your security requirements.
Describe the Bug
Trying to copy a repo via HTTPS where an authentication to the repository is required fails.
The error message:
Expected Behavior
Define base_auth_(username|password) and git should be able to fetch the repository.
Steps to Reproduce
Steps to reproduce the behavior:
Environment
Additional Context
https://username:[email protected]
syntax does not solve the issue.The text was updated successfully, but these errors were encountered: