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
Is your feature request related to a problem? Please describe.
We have created our own Powerpipe Mod in a private GitLab repository. Unfortunately it seems like right now authentication to mod repositories (when installing via Powerpipe) only supports the way how GitHub does it (https://github.com/turbot/pipe-fittings/blob/d7decaf1e82d8538970cc7d7821d5a8f1c3994d4/modinstaller/git.go#L86-L104), i.e. with the token as username or token as password and "x-access-token" as the username.
Describe the solution you'd like
I'd like a way where I'm able to define the basic auth credentials freely, so that I can make GitLab authentication work. In GitLab for example the username is "gitlab-ci-token" and the password is a token provided via $CI_JOB_TOKEN. Bonus points for being able to configure the credentials for each host, similar to how .git-credentials does it (https://git-scm.com/docs/gitcredentials).
Describe alternatives you've considered
I've tried using this style of repo HTTPS urls https://username:[email protected], it didn't work (I guess URL parsing fails). I've tried setting credentials via the .git-credentials file $HOME and hoped that the used git SDK would implicitly look for credentials there - unfortunately not. My fallback scenario now was doing a git clone beforehand and then pointing Powerpipe to the local folder, which is not optimal.
The text was updated successfully, but these errors were encountered:
Hey @talpa-robin, thanks for raising this issue. This would be a great enhancement, but currently, we don't have plans to support this yet. But surely, this would be a great addition. If you're interested in working on it, please go ahead (we love user contributions).
Hey @pskrbasu, sure, could try that. Doesn't seem to be too complicated (at least supporting basic auth in the GitUrl). It seems to be a change in the https://github.com/turbot/pipe-fittings/blob/develop/modinstaller though. Any documentation of advice on how to test changes to the pipe-fitting directly with powerpipe?
@talpa-robin Apologies for the delay(I was out on vacation). Please take a look at the Developing section. You will need to add a replace in your powerpipe go.mod file that directs it to your local pipe-fittings repo changes, to test the local pipe-fitings changes.
Is your feature request related to a problem? Please describe.
We have created our own Powerpipe Mod in a private GitLab repository. Unfortunately it seems like right now authentication to mod repositories (when installing via Powerpipe) only supports the way how GitHub does it (https://github.com/turbot/pipe-fittings/blob/d7decaf1e82d8538970cc7d7821d5a8f1c3994d4/modinstaller/git.go#L86-L104), i.e. with the token as username or token as password and "x-access-token" as the username.
Describe the solution you'd like
I'd like a way where I'm able to define the basic auth credentials freely, so that I can make GitLab authentication work. In GitLab for example the username is "gitlab-ci-token" and the password is a token provided via $CI_JOB_TOKEN. Bonus points for being able to configure the credentials for each host, similar to how .git-credentials does it (https://git-scm.com/docs/gitcredentials).
Describe alternatives you've considered
I've tried using this style of repo HTTPS urls https://username:[email protected], it didn't work (I guess URL parsing fails). I've tried setting credentials via the
.git-credentials
file $HOME and hoped that the used git SDK would implicitly look for credentials there - unfortunately not. My fallback scenario now was doing a git clone beforehand and then pointing Powerpipe to the local folder, which is not optimal.The text was updated successfully, but these errors were encountered: