elsa-workflows/elsa-core

ApiWorkflowProvider

Open

#1,109 opened on Jun 9, 2021

View on GitHub
 (10 comments) (0 reactions) (1 assignee)C# (979 forks)batch import
enhancementgood first issueprio lowtriaged

Repository metrics

Stars
 (5,486 stars)
PR merge metrics
 (Avg merge 1d 17h) (29 merged PRs in 30d)

Description

We currently have 3 workflow providers:

ProgrammaticWorkflowProvider: provides workflow blueprints based on the workflows coded with the fluent Workflow Builder API. DatabaseWorkflowProvider: provides blueprints based on those stored in the database (JSON models stored by the designer). StorageWorkflowProvider: provides blueprints based on JSON files stored on some hard drive or blob storage such as Azure Blob Storage.

We should have a fourth provider that uses the Elsa API endpoints to get workflows from.

Then client apps that run Elsa locally won't have to invoke the Elsa API, but instead take advantage of the workflows provider model.

Contributor guide

Research direction
Study the existing workflow providers (Programmatic, Database, Storage) to understand the IWorkflowProvider interface. Then implement a new ApiWorkflowProvider that fetches workflow blueprints from the Elsa API endpoints. Look at how the other providers load and cache blueprints.
Tech stack
csharp
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.
1-3 hours
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.
Clear
Prerequisites
C#.NETFamiliarity with the Elsa workflow providers pattern
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60