can not add repo url
jesusys opened this issue · 3 comments
Describe the bug
A clear and concise description of what the bug is.
when add a repo and it shows a failure with the message:
yaml: line 3: mapping values are not allowed in this context
To Reproduce
Steps to reproduce the behavior:
- Go to 'template'
- Click on 'add templates reference'
- Scroll down to 'Repository URL'
- my repo is "https://llm-gitlab.xxxxxx.com/xxxx/xxxxx"
- if i change repo to "https://llm.xxxxxx.com/xxxx/xxxxx" or "https://gitlab.xxxxxx.com/xxxx/xxxxx" is ok
Expected behavior
A clear and concise description of what you expected to happen.
i think repo name can't exist "-"
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [all]
- Browser [e.g. chrome,edge]
- Version [0.7.1/0.10.0]
Hey @jesusys, thanks for the issue.
I haven't tried fetching a template from a self-hosted GitLab. It's weird that it works on those hosts but not on llm-gitlab.
Judging by the message, I'd say that its the problem with Chart.yaml
. Could you check if that file is correct.
If you think it might be easier, you can join our Discord, and we can try to debug it. Feel free to start a thread in the #questions
Hey @jesusys, thanks for the issue.
I haven't tried fetching a template from a self-hosted GitLab. It's weird that it works on those hosts but not on llm-gitlab.
Judging by the message, I'd say that its the problem with
Chart.yaml
. Could you check if that file is correct.If you think it might be easier, you can join our Discord, and we can try to debug it. Feel free to start a thread in the #questions
nobody reply me in discord. i clone the demo to my gitlab. , if host url is xxx.abc.com ,i can add template , if hosts url is xxx-yyy.abc.com, i can't add template.
i test cyclops-ctrl/internal/template/git.go , func clone(repoURL, commit string, creds *auth.Credentials) (billy.Filesystem, error) api or interface,i can get gitlab's repo from host url xxx-yyy.abc.com.
@petar-cvit
@jesusys, can we consider the issue resolved? If not, let us know what needs to be changed