Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-1167

Add persistence to workflows via software template

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None
    • orchestrator-workflows
    • None

      Until https://issues.redhat.com/browse/SRVLOGIC-265 is implemented, we'll have to enable persistence for long-running workflows explicitly.

      The solution requires extending the software template to enable persistence if selected by the user.

      By enabling persistence to the workflow, the generated Sonataflow CR needs to be extended to contain the persistency attributes:

        persistence:
          postgresql:
            secretRef:
              name: postgres-secrets
              userKey: POSTGRES_USER
              passwordKey: POSTGRES_PASSWORD
            serviceRef:
              name: postgres
              port: 5432
              databaseName: sonataflow
              databaseSchema: callbackstatetimeouts

      As specified in https://github.com/apache/incubator-kie-kogito-docs/pull/529/files#diff-36629490942c3ebc783d7315dafa3098c8196d8eb1d3f089598e35dbc66a1468R85

       

      Additional changes are mentioned in this thread:

      https://redhat-internal.slack.com/archives/C059YMMB664/p1711439937631139?thread_ts=1710956396.563349&cid=C059YMMB664

       

      The acceptance criteria are:

      1. Having a software template that provides persistence capability to the created workflow

            rh-ee-gfarache Gabriel Farache
            masayag@redhat.com Moti Asayag
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: