Uploaded image for project: 'Serverless logic'
  1. Serverless logic
  2. SRVLOGIC-8

[core] Workflow basic constructs

    XMLWordPrintable

Details

    • Feature
    • Resolution: Done
    • Blocker
    • 1.24.0
    • None
    • serverless-workflow
    • None
    • False
    • None
    • False
    • 0
    • 0% 0%
    • 2022 Week 32-34 (from Aug 8)

    Description

      Motivation

      Basic constructs of Serverless workflow specification are essential capabilities to make workflow definitions possible.

      Goal

      Provide the basic workflow constructs

      Scenarios

      As a developer, I need to identify my workflow and its future versions so that I can trigger the right workflow definition and version.

      As a developer, I need to define data inputs and validate them according to the given JSON schema so that the workflow and services receive correct data.

      As a developer, I need to modify the payload so that the function gets the data structure it expects.

      As a developer, I need to make data-based and event-based decisions so that workflow can transition to various flow branches.

      As a developer, I need actions and remote services to be processed in parallel so that they do not block each other.

      As a developer, I need to define workflow states which are processed for each element of a data array so that the operations and services execute once for each array element.

      As a developer, I want to break down a workflow and move some states to a subflow so that I can keep the workflows simple.

      Expected outcomes

      Targeting partial support of Serverless workflow 0.8 spec. This is the full list of serverless workflow constructs: https://docs.google.com/document/d/1QUcW7wkKAElBXxd8wtEX9gkpodUcFN6dUxsL_HcTRL8/edit#

      Basic workflow constructs are functional and follow the Serverless workflow specification in the engine.

      Within the basic constructs and globally JQ is the recommended type of expressions.

      Paralell state processes actions one by one sharing the same execution thread - best to use with asynchronous calls.

      Subflows have to be part of the same project. Otherwise it’s possible to call another workflow service via operation state and OpenAPI.

      Versioning - write documentation on how to version processes with the use of Knative Serving Revisions and stating known limitations (in persistent storage, etc.)

      Out of scope

      Sleep state

      Data output schema validation is out of scope (on going discussion to add in v0.9 spec)

      Parallel state multitasking is out of scope SRVCOM-1851.

      Attachments

        Issue Links

          incorporates

          Feature Request - Feature requests from customers and/or users KOGITO-7113 Use Quarkus Extension OpenAPI client gen VI: Modify examples to use the extension

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Feature Request - Feature requests from customers and/or users KOGITO-7391 Validate references and required properties of SW definitions file during codegen

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. KOGITO-6996 [KSW-Guides] How to deal with parallelism in Serverless Workflow

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7257 [KSW-Guides] Accessing Workflow Metainfo in Runtime

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7259 [KSW-Guides] Defining an input schema for Workflows

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7293 [KSW-Guides] CNCF Serverless Workflow specification support

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-6984 [KSW-Guides] How to configure Kogito SW Services with Knative Service Revisions

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-6773 [KSW] dataInputSchema should be used as the input model for KSW services

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-6985 [KSW] - Persistence: add workflow id and version as the constraint keys when persisting the flow state

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) KOGITO-6986 [KSW] - Implement DataOutputSchema for Workflows (specification tracking)

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Resolved
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-6967 constants.getref returns null when the uri is set

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-6968 dataInput returns null when inline

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. SRVLOGIC-6 [core] Parallel state multitasking in workflows

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Activity

            People

              ftirados Francisco Javier Tirado Sarti
              ibek1@redhat.com Ivo Bek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: