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
Doing this in a secure system needs some kind of way to inject a secret. Currently I am able to inject an environment variable containing such a secret, however when running:
I wonder if it is better to allow injecting a ".gitcookies" file and configuring http to use cookies - which is slightly better than static passwors / netrc, as it is pre-authenticated cookie (which can be easily rotated/expired/logedout etc).
The git-checkout pipeline does not appear to have any paramaters or obvious ways to authenticate against a private repository.
Typically the easiest way to get authentication in to a clone or checkout is by manipulating the git URI, I.E.:
git clone https://$username:$password@gitlab.com/privaterepo
Doing this in a secure system needs some kind of way to inject a secret. Currently I am able to inject an environment variable containing such a secret, however when running:
$GIT_SECRET
does not appear to be evaluated and authentication fails as if it weren't there.As a workaround currently, I can use:
Thanks!
The text was updated successfully, but these errors were encountered: