Graylog2/graylog2-server

Deleting or renaming a pipeline rule should update corresponding references in the pipelines

Open

#21,162 opened on Dec 11, 2024

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Java (1,032 forks)batch import
good first issueimprovementtriaged

Repository metrics

Stars
 (6,945 stars)
PR merge metrics
 (Avg merge 8d 19h) (297 merged PRs in 30d)

Description

When a pipeline rule is deleted or renamed, we do not update affected pipelines. Invalid references are left over. It looks messy and forces the user to explicitly remove or update the rule wherever it had been used. GL has the ability to do this on behalf of the user.

Your Environment

  • Graylog Version: 6.2

Contributor guide

Research direction
Investigate how pipeline rules are stored and referenced by pipelines. Look for classes like PipelineRule, Pipeline, and related services. Focus on the deletion or renaming logic, and explore how to cascade changes to references in affected pipelines.
Tech stack
java
Domain
backend
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.
Half day
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
GitJava
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40