We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
/
Either it shouldn't be possible to create a repository with an invalid token or the sync should work as expected
The synchronization fail with an exit code of 128 and the following messages
Test Wrong token
test
qwertytrew/qewrtsdfgtrew
https://github.com/networktocode-llc/nautobot-datasource
2021-05-01T20:25:14.013404 | Failure | | Cmd('git') failed due to: exit code(128) cmdline: git clone -v --progress https://test:qwertytrew/qewrtsdfgtrew@github.com/networktocode-llc/nautobot-datasource /opt/nautobot/git/test-wrong-token 2021-05-01T20:25:14.045399 | Failure | | Error while refreshing Test Wrong token: Cmd('git') failed due to: exit code(128) cmdline: git clone -v --progress https://test:qwertytrew/qewrtsdfgtrew@github.com/networktocode-llc/nautobot-datasource /opt/nautobot/git/test-wrong-token
The text was updated successfully, but these errors were encountered:
Thanks for the report! Looks like we probably need to url-encode the token when we add it to the URL in ensure_git_repository().
ensure_git_repository()
Sorry, something went wrong.
URL escape special characters in Git repository username/password. Fixes
ef2cd2f
#397
f3d816d
#397 (#425)
glennmatthews
Successfully merging a pull request may close this issue.
Environment
Steps to Reproduce
/
Expected Behavior
Either it shouldn't be possible to create a repository with an invalid token or the sync should work as expected
Observed Behavior
The synchronization fail with an exit code of 128 and the following messages
Test Wrong token
test
qwertytrew/qewrtsdfgtrew
https://github.com/networktocode-llc/nautobot-datasource
The text was updated successfully, but these errors were encountered: