goharbor/harbor

Add Webhook Trigger for “Tag Created” Event

Closed

#22,640 opened on Dec 15, 2025

View on GitHubContributor guide
 (6 comments) (0 reactions) (0 assignees)Go (5,235 forks)batch import
Stalehelp wanted

Repository metrics

Stars
 (28,490 stars)
PR merge metrics
 (Avg merge 8d 17h) (74 merged PRs in 30d)

Description

Discussed in https://github.com/goharbor/harbor/discussions/22635

Originally posted by yashid-mohamed December 11, 2025 I’d like to request a new webhook event type that triggers specifically when a tag is created (without requiring the artifact itself to be pushed again).

Problem

When performing tag promotion (e.g., promoting an existing digest from 0.403.0 → 0.403.0-prod) using the Harbor API or UI, Harbor currently does not emit any webhook for this action.

This creates a gap for CI/CD pipelines and downstream automation tools that rely on webhook notifications to react to new tags. Since no new artifact is pushed and no scan/build occurs, none of the existing webhook types fire.

Use Case

Many promotion workflows rely on copying or creating tags inside Harbor (to preserve digest immutability and avoid re-pushing images). Examples:

  • Promotion from dev → prod
  • Tagging releases in automation pipelines
  • Triggering deployments based on tag creation

Without a webhook event for tag creation, external systems must continuously poll Harbor, which is inefficient.

Contributor guide

Research direction
Study the existing webhook implementation in Harbor, particularly how events like artifact push are defined and triggered. Identify where tag creation occurs (e.g., in tag handler or API) and add a new webhook event type for tag creation following the existing pattern.
Tech stack
go
Domain
backendapidevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60