wmedvede commented on PR #367:
URL: 
https://github.com/apache/incubator-kie-kogito-serverless-operator/pull/367#issuecomment-1924238590

    @dmartinol @ricardozanini @domhanak some positive feedback for the record.
   
   I have executed **usecase-oc** 
https://github.com/flows-examples/techpreview2/blob/f39a25e626e217dabf7b69237641ca1e05375c6a/README.md?plain=1#L739
   
   And I can see this results:
   
   **Managed and normal properties are created** 
   ![Screenshot from 2024-02-02 
17-18-38](https://github.com/apache/incubator-kie-kogito-serverless-operator/assets/2431454/7a8618fd-f1ce-449f-a0a2-664c87fe180e)
   
   **I've added a service discovery property manually in the 
callbackstate-props**
   
   ![Screenshot from 2024-02-02 
17-18-59](https://github.com/apache/incubator-kie-kogito-serverless-operator/assets/2431454/609cb94a-46f9-4e21-b29b-179b8b7a64b9)
   
   Then I went to the managed properties and I can see that the service 
discovery was produced and the corresponding property is in the managed set. 
The other managed properties are still there. good!
   
   
   ![Screenshot from 2024-02-02 
17-19-21](https://github.com/apache/incubator-kie-kogito-serverless-operator/assets/2431454/53f739e6-9158-408a-be72-5b0c942b775a)
   
   - The workflow  is running well I could create instances and see them in the 
DI, good!
   
   - When I add properties manually to the user properties I can then see the 
workflow rollingout. good!
   
   
   - In the workflow deployment environment I can't see any property
   But maybe we can start moving things there in a follow-up PR. If I 
understood well, we should start to see there this kind of props
       quarkus.http.port = 8080
       quarkus.http.host = 0.0.0.0
   as env vars.
   
   But we can think about this in follow-up PR
   
   
![image](https://github.com/apache/incubator-kie-kogito-serverless-operator/assets/2431454/553f1d03-0706-4c91-ab6f-d6097d1ed0ba)
   
   
   good job @dmartinol !!!!
   
   
   
   
   
   


-- 
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