404 Project Not Found

[chris-rutherfurd]

I have a read only personal access token to my cloud Gitlab account all setup with a wildcard rule to pickup all projects.

Logging into the kubernetes log stream it lists out several of the projects in my Gitlab account correctly but gives a error

"error":"GET https://gitlab.com/api/v4/projects/repo-name/repository/branches: 404 {message: 404 Project Not Found}","level":"warning","msg":"pulling refs from project","project-name":"repo-name","time":"2022-05-23T13:48:34Z"}

It is correctly connedcting to the API it appears as there is an info message reported right before the not found warnings saying,...

{"level":"info","msg":"scheduling refs from projects pull","projects-count":29,"time":"2022-05-23T13:48:32Z"}

My helm values.yml file has the following for the config values...

config:
  gitlab:
    token: #### Personal Access Token ####
    url: https://gitlab.com
  wildcards:
    - {}

[acericdev]

Same for me, I analysed it, and it does require the project id rather than the project path ... waiting for fix or maybe a setup config somewhere

[brandonjwk]

Looks like you can use namespaced names in addition to id.