Open PatrickLaabs opened 1 year ago
Sorry, we missed that issue.
It's probably a bug, maybe the CLI isn't using the token for fetching the gitops-template
repository. It should work though if you provide a token with proper access. I don't think we tested this user case, we'll give it a closer look, thanks for the report.
I can reproduce the issue, let me check with the engineering team.
Confirming this issue still exists:
{"level":"error","time":"2024-06-28T22:31:07Z","message":"error cloning repo (https://github.com/capswan/gitops-template) at: /root/.k1/cscloud/gitops, err: authentication required"}
{"level":"panic","time":"2024-06-28T22:31:07Z","message":"error opening repo at: /root/.k1/cscloud/gitops, err: authentication required"}
{"level":"info","time":"2024-06-28T15:31:10-07:00","message":"unable to get cluster 500 Internal Server Error, continuing"}
{"level":"info","time":"2024-06-28T15:31:20-07:00","message":"unable to get cluster 500 Internal Server Error, continuing"}
Which version of kubefirst are you using?
v2.0.8
Which installation type?
k3d (local)
Which distributed Git provider?
GitHub
What is the issue?
(This is not about the already known issue #1548)
Currently, if a user wants to work with it's own gitops-template repository, the user has to either fork or clone the repository. Forking the gitops-template repository forces the user to keep the repo publicly visible and also available.
If one may decide to switch the visibility to private, the user has to clone the repo, and add the needed tag (See #1548).
The "Problem": Using a private gitops-template repo will fail, since the kubefirst cli is not able to access the repo, even if the github_token environment variable is set and valid.
Since I don't know if this is a bug, or not: This Issue might be also a feature / improvement request.
Snippets from the log:
Code of Conduct