Open alberthuang24 opened 3 years ago
I fixed it by temporarily modifying spec.cluster.gitServer.
apiVersion: core.jenkins-x.io/v4beta1
kind: Requirements
spec:
autoUpdate:
enabled: false
schedule: ""
cluster:
chartRepository: http://bucketrepo.jx.svc.cluster.local/bucketrepo/charts
clusterName: kind
devEnvApprovers:
- todo
environmentGitOwner: todo
gitKind: github
gitName: github
- gitServer: https://github.com
+ gitServer: https://<your github token>@github.com
provider: kubernetes
registry: ghcr.io
Cannot believe passing the raw token on a repository is the unique solution to this. Unbelievable.
Agree with you @jrx-sjg
jx admin install support ssh protocol url.
Will take a look this holidays. It would be good to use ssh keys to do the git operations
A bit confused though, u should not have to specify access token in the requirements file. Check: https://jenkins-x.io/v3/develop/faq/using/#how-do-i-stop-jx-asking-for-git-credentials
May be I am missing something?
In today. users of github using the
jx import
command should get an error like mineThe reason for this seems to be that the https clone dev repo is used here.
Possible solutions
jx admin install support ssh protocol url.
Reference
https://github.blog/2020-07-30-token-authentication-requirements-for-api-and-git-operations/