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

Aborting a workflow should send DELETE to workflow running instance

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • orchestrator-ui
    • False
    • Hide

      None

      Show
      None
    • False

      In the orchestrator-backend plugin, the abort action is implemented by using the DataIndex as a gateway for aborting a workflow.

      As recommended by sonataflow's maintainer, to abort a workflow, a DELETE should be send to the workflow running instance.

      Therefore the implementation should be changed.
       

      A sample of curl request to abort a workflow:

      curl -X DELETE http://create-ocp-project-sonataflow-infra.apps.ocp414.lab.local/management/processes/create-ocp-project/instances/afd7322c-4f75-4442-b508-1b3c1c11b0dd    -H "Content-Type: application/json"

            [FLPATH-1676] Aborting a workflow should send DELETE to workflow running instance

            So is the operation delete or abort? After aborting and deleting is the instance gone?

            Bat-Zion Rotman added a comment - So is the operation delete or abort? After aborting and deleting is the instance gone?

              ydayagi yaron dayagi
              masayag@redhat.com Moti Asayag
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: