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

[DOC] Serverless workflow guides in the community

    XMLWordPrintable

Details

    • False
    • None
    • False
    • 2022 Week 32-34 (from Aug 8)

    Description

      Motivation

      New service orchestration capabilities in OpenShift Serverless should have new documentation describing how to get started.

      Goal

      Write and publish new Getting started with Serverless workflows (name TBD) documentation

      Scenarios

      Red Hat nurtures self-service adoption so we should target OpenShift Developer Sandbox for the first trial getting started experience

      Expected outcomes

      New Getting started with Serverless workflows (name TBD) documentation published in the community - it cannot be part of official OpenShift Serverless docs until we reach tech-preview state.

      A service orchestration example on OpenShift Developer Sandbox ( which can be deployed manually. It doesn’t have to be a guided example inside OpenShift console )

      Attachments

        Issue Links

          incorporates

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-7134 Create and publish KSW Website

          • 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-7290 [KSW-Guides] Handling events on workflows

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. KOGITO-6806 [KSW-Guides] Serverless Workflow with the Saga example

          • 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-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-6998 [KSW-Guides] Instruct how to have different endpoint configuration profiles for OpenAPI calls

          • 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-7267 [KSW-Guides] Consuming and producing events on Knative Eventing

          • 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-7288 [KSW-Guides] Event correlation with 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-7301 [KSW-Guides] Persistence with PostgresSQL databases

          • 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-7636 [KSW-Guides] SW configuration properties guide

          • 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-6854 [KSW-Guides] Create a Getting Started for SW Quarkus guide

          • 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 documented by

          Sub-task - The sub-task of the issue KOGITO-7226 [DOC] Review guide - Create your first workflow service

          • 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

          Activity

            People

              rhn-support-zanini Ricardo Zanini Fernandes
              ibek1@redhat.com Ivo Bek
              Zbynek Drapela Zbynek Drapela
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: