Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support ignore event in notifications #5035

Closed
klbjlabs opened this issue May 24, 2018 · 2 comments
Closed

support ignore event in notifications #5035

klbjlabs opened this issue May 24, 2018 · 2 comments
Labels
community needs/triage triage issue before assigning

Comments

@klbjlabs
Copy link

When will this feature can be support in Harbor?

In current version ( v1.5.0 ), The jobservice auto trigger so many pull events. (this morning I get 1000+ events post)

And if you click this button, you will get 82 pull events (The number depends on how many versions you have.).
default
[

@klbjlabs klbjlabs changed the title ignore event in notifications support ignore event in notifications May 24, 2018
@klbjlabs
Copy link
Author

@steven-zou

@reasonerjt
Copy link
Contributor

reasonerjt commented May 25, 2018

@klbjlabs

  1. The patch is not part of a released registry, we don't have the plan to build the master branch to put it in Harbor' release.
  2. I didn't have a chance to test, but if only filters out application/octet-stream mediatype it probably doesn't fix the problem you are seeing. If it's configured to filter out all pull notifications the access log will not work.

Do you see any perf issues when there are many events? I suggest you patch Harbor with latest registry code and manually edit config.yml for now.

@reasonerjt reasonerjt added community needs/triage triage issue before assigning labels May 25, 2018
@klbjlabs klbjlabs closed this as completed Jun 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community needs/triage triage issue before assigning
Projects
None yet
Development

No branches or pull requests

2 participants