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
This uses GITHUB_OAUTH_TOKEN to authenticate for private GitHub repos. When using GitLab, the common use case is to use deploy tokens.
There should be a variable or automatic way to tell module-installer that the repo is from GitLab, in order to use variables for both the token's username (or if a username isn't provided, should use the default gitlab) and token (or using a variable GITLAB_TOKEN env var). e.g:
When using module-install, it assumes the repo origin is from GitHub, e.g:
module-install --module-name 'install-rundeck' --repo 'https://github.com/craftech-io/module-ci' --tag 'v0.0.1'`
This uses GITHUB_OAUTH_TOKEN to authenticate for private GitHub repos. When using GitLab, the common use case is to use deploy tokens.
There should be a variable or automatic way to tell
module-installer
that the repo is from GitLab, in order to use variables for both the token's username (or if a username isn't provided, should use the defaultgitlab
) and token (or using a variableGITLAB_TOKEN
env var). e.g:using flags:
module-install --module-name 'install-rundeck' --gitlab-token-username username --gitlab-token <token> --repo 'https://gitlab.com/private-repo' --tag 'v0.0.1'
using env vars:
or
The text was updated successfully, but these errors were encountered: