xaleeks
xaleeks
So the to-dos here are 1. define the resolution logic when multiple resources exist that define the same route aka URL 2. Identify any exceptions to the above if we...
I know exactly what you are talking about but the current proprietary token service in Harbor does not allow for that, a robot at its highest degree of freedom will...
@MichaelKueller Labels as a filter condition was removed shortly after it was released, it was causing some issues because of how they are created at system and project level but...
Agreed. Ideally it comes from some config system or CI/CD pipeline so we have full audit capabilities, know who made what changes and can tie this back to the specific...
agreed, makes sense for a lot of customers
@cafeliker Thanks, I think it looks good.
vulnerability information are readily available to users on UI whenever they perform image scan. There is also a webhook (in next release) to send notification after image scan performed. So...
The webhook notification from running a scan is instantaneous, he(project owner) just needs to configure an action listener (permission'ed by the security team). https://goharbor.io/docs/1.10/working-with-projects/project-configuration/configure-webhooks/
can you expand? how does this save a lot of replication rules? @phin1x
Nick, are we ready to begin to pick this up within the next couple releases? Regarding granularity, I absolutely agree that we start at global instance level and move down...