Closed benedeki closed 4 months ago
An idea emerged
Flows are created only when a partitioning is created too. Therefor that partitioning is kind of identifying for the flow. Adding that connection and field of partitioning into flows.flows
(the actual json not the foreign key) makes the flow much more identifiable, compared to Flow 1234.
Will create a PR.
Background
Flows are starting to show their values as information over different runs are required. But they are hard to work with and identify.
Questions To Answer
Desired Outcome
An easy and "user" friendly way, how to identify a flow and request its data. (By user is not meant an end-user, but a user of Atum -either the Atum Agent or Atum Service API).