great, I've created a ticket therefore:
https://issues.apache.org/jira/browse/STREAMPIPES-628
Best
Tim
Am 14.11.2022 21:22 schrieb Dominik Riemer:
Hi Tim,
good question.
I think we just never added the "system" flag to pipelines created in
StreamPipes Connect.
Before we added user management, the "own" endpoint only gave you
pipelines created by the current user. As of now, the "own" endpoint
returns all pipelines a user has read access to.
So I think we could create a ticket to properly flag system-created
pipelines and also maybe to mark them as read-only in the pipeline
overview, similar to the StreamPipes Conenct-created adapters in the
installation view.
Cheers
Dominik
-----Original Message-----
From: Tim <[email protected]>
Sent: Monday, November 14, 2022 8:58 PM
To: Dev <[email protected]>
Subject: [DISCUSS] Automatically created "Persist *" Pipeline is
flagged as "own"
Hi everyone,
I was playing around a bit with our StreamPipes API and observed the
following.
When creating an adapter and selecting "Persist events" in the last
dialog so that all events are written directly to the data lake,
StreamPipes automatically creates a pipeline to do this.
When I query pipelines from the StreamPipes API, I'd expect to get
this pipeline via the "system endpoint " since it was created by the
system.
However, the pipeline was only accessible via the "own pipelines"
endpoint.
What is your opinion? Is this the correct behavior?
What differentiates "own" pipelines from "system" pipelines?
Maybe I just haven't got the point here ;)
Best
Tim
