You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pipeline connections are deleted/removed after deleting a pipeline or stream
Current Behavior
After deleting a stream or pipeline, Entries remain in the connections
Attempting to modify a connection through the API results in "Stream <> not found!" or "No pipeline with id " responses.
Possible Solution
a DELETE endpoint /system/pipelines/connections/<connection_id> to be able to clear out an empty stream ID
When a pipeline is deleted, the pipeline is cleared from all stream connections
When a stream is deleted, it is removed from the connections
Steps to Reproduce (for bugs)
Create a Stream
Create a pipeline
Connect stream to pipeline
Delete Stream, or Pipeline
Response data from GET /system/pipelines/connections still contains data for deleted stream/pipeline
Context
I was playing around with the API, and noticed this behavior when trying to write a script to automate some tasks, that connections stick around.
Your Environment
Graylog Version: 5.2.6/6.0.4
Java Version:
OpenSearch Version:
MongoDB Version:
Operating System:
Browser version:
The text was updated successfully, but these errors were encountered:
Expected Behavior
Pipeline connections are deleted/removed after deleting a pipeline or stream
Current Behavior
After deleting a stream or pipeline, Entries remain in the connections
Attempting to modify a connection through the API results in "Stream <> not found!" or "No pipeline with id " responses.
Possible Solution
a DELETE endpoint
/system/pipelines/connections/<connection_id>
to be able to clear out an empty stream IDWhen a pipeline is deleted, the pipeline is cleared from all stream connections
When a stream is deleted, it is removed from the connections
Steps to Reproduce (for bugs)
GET /system/pipelines/connections
still contains data for deleted stream/pipelineContext
I was playing around with the API, and noticed this behavior when trying to write a script to automate some tasks, that connections stick around.
Your Environment
The text was updated successfully, but these errors were encountered: