LuboTerifaj opened a new issue, #1970:
URL: https://github.com/apache/incubator-kie-kogito-examples/issues/1970

   ### Description
   
   Update 
[serverless-workflow-foreach-quarkus](https://github.com/apache/incubator-kie-kogito-examples/tree/stable/serverless-workflow-examples/serverless-workflow-foreach-quarkus)
 example.
   
   #### Issues
   - There is a wrong esxpected output from a request command in readme file:
     - `curl -X POST -H 'Content-Type:application/json' -H 
'Accept:application/json' -d '{"input": [1,2,3]}' http://localhost:8080/foreach`
     - Readme file result:
       ```
       { 
         "workflowdata": {
               "output": [
                   2,
                   3,
                   4
               ]
           }
        }
       ```
     - Application result: 
`{"id":"c9e6815d-9363-44fd-bd9f-29c7e0813cef","workflowdata":{"output":[4,6,8]}}`
   - "Building and Deploying Workflow using CLI + Kogito Serverless Workflow 
Operator" section should be rewritten.
     - Wrong URLs in readme file:
       - "For this prepare your environment by following the instructions from 
[here](https://github.com/apache/incubator-kie-kogito-examples/blob/stable/serverless-workflow-examples/serverless-workflow-foreach-quarkus)."
         - References the current readme file. It doesn't make sense to 
reference the same readme file here.
       - "Refer to [Serverless Workflow 
Guide](https://github.com/apache/incubator-kie-kogito-examples/blob/stable/serverless-workflow-examples/serverless-workflow-foreach-quarkus),
 to know how to build and deploy workflows using CLI + Kogito Serverless 
Workflow Operator.'
         - References the current readme file, which is most likely a mistake.
     - It would make sense to add at least some introduction why would somebody 
follow the instructions in this section.
   
   ### Acceptance criteria
   All issues listed above are resolved. 
   
   ### Implementation ideas
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to