Best practice for a robot to push/pull from multiple projects?

[flixman]

I am in the process of setting up Harbor as a registry for my homelab, in which I have multiple projects. I am using a runner to perform the CI of my applications and the approach I am taking is to have a project-level robot that has push/pull permissions to all projects.

The problem, now, is: to the robot because a new project has been added, using the CLI, I am unable to get all the project robots in the system: I need, seems, to know one project this robot is used on, query it, then get the robot id... and then update that robot to get the new project added? (I am still figuring out this part).

Is this the correct way to address this problem, or is better to have a system-level robot with push/pull to all namespaces? I'd prefer my current approach, as it would allow me to skip the robot from gaining access to repos it might not need.

Thank you!

[flixman]

Ok, I understood what was wrong in my question: The robots associated to a project can only have one set of permissions, which can be replaced by another. What I want requires a system-level robot, because those can have multiple permission sets, one per project.