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

Workflow quick authoring

XMLWordPrintable

    • Workflow quick authoring
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      Assumptions:

      1. A workflow (as a  ) has already been defined, and is stored in a Git repository
      2. This Git repository has already a CI/CD pipeline defined where each code modification produces a new container image and deploys it. 
      3. The orchestrator-backend can interact programatically with the workflow's Git repository.

      We could offer a similar experience, a la GitHub Actions, where after editing a workflow definition the user is prompted to commit the changes.

      Here is an example of the prompt displayed after editing a GitHub Action definition file:

       

              Unassigned Unassigned
              jkilzi@redhat.com Jonathan Kilzi
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: