-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure serverless-workflow-examples are working properly #1860
Comments
For the record, the serverless-workflow-timeouts-showcase-extended example was addressed here #1857 |
@LuboTerifaj, here #1863 there are some changes on the examples to avoid using the quay.io/kiegroup/kogito-runtime-jvm:latest, and changing the referenced image at the docker compose by the nightly one to see the latest changes. Even I applied the changes in the serverless-workflow-examples, I just focused my testing cases in mainly working with docker-compose:
Let's see how it goes, once the pr is merged we can add the check to that ones (at least) |
@LuboTerifaj here #1870 serverless-workflow-newsletter-subscription have been also updated and verified that is working properly |
Hello @gmunozfe , I am reassigning the issue to you for checking the remaining examples. Please see the description of the issue to understand its goal. Should you have any questions, don't hesitate to reach out to me. Thanks! |
Description
Some serverless-workflow-examples may not work properly.
Goal
Report individual issues for all examples that do not work properly.
Link all found issues in the comments.
Scope
Please mark the example below as checked once it is reviewed and all found issues are reported. Those issues don't have to be resolved as part of this issue.
The goal of this issue is to identify issues in examples. The found issues resolution is out of scope, although welcomed.
Examples to be checked
Acceptance criteria
All issues are regarding examples are reported and linked to this issue.
Implementation ideas
No response
The text was updated successfully, but these errors were encountered: