Flow System (BE)

[zaychenko-sergei]

Represents Backend-side work that should feed frontend Task System FE epic.

Tasks:

• GraphQL: support live updates of Flows when their state evolves #275
• Introduce Admin users #276
• Authorization checks for Tasks GraphQL API #277 (needs to be reconsidered)
• GraphQL: Administrators view of Executors #278
• Prototype internal Event Bus (pub-sub) #279
• Flows: introduce a component to store dataset flows schedule settings #280
• GraphQL: Administator's view of tasks #281
• Flows: support Flow History feature #282
• Flows: provide GraphQL API to schedule manual dataset flow #283
• Flows: implement automatic flow scheduler based on the user settings #284
• kamu ui: new flag to allow/disallow changing automatic dataset updates schedule #285
• Store and stream task execution logs #286
• Flows: Extend DatasetPermissions GraphQL type with canSchedule flag #287
• Flows: Fully support CRON expressions in the Flows System #396
• Flows: Design and implement GraphQL API to support Dataset Flows UI view features #397
• Flows: Provide GraphQL API to manually cancel flow's schedule tasks #398
• Flows: model simple scoring function to prioritize running flows in the same time slot #399
• Flows: retry logic for failed tasks #400
• Flows: properly support batching/throttling conditions #401
• Flows: Automatically pause flow schedules if dependent tasks are failing  #419
• API: Get all accounts that launched the dataset flow #613

[sergiimk]

I have created a combined Product swimlane in our roadmap and moved the tracking of backend tasks into kamu-data/kamu-web-ui#170