-
Notifications
You must be signed in to change notification settings - Fork 59
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
kie-kogito-docs-557: Add Newsletter subscription use case #558
Conversation
@kaldesai can you please take a look? |
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
|
||
== Executing the workflows | ||
|
||
In a command terminal, clone the `kogito-examples` repository, navigate to the cloned directory, and follow link:{kogito_sw_examples_url}/serverless-workflow-newsletter-subscription/README.md#running-on-knative[these steps]: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In a command terminal, clone the `kogito-examples` repository, navigate to the cloned directory, and follow link:{kogito_sw_examples_url}/serverless-workflow-newsletter-subscription/README.md#running-on-knative[these steps]: | |
In a command terminal, clone the `kogito-examples` repository, navigate to the cloned directory, and follow the link:{kogito_sw_examples_url}/serverless-workflow-newsletter-subscription/README.md#running-on-knative[these steps]: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kaldesai 'link' in this case is not shown, it's just a key to create the following link.. It will be shown like: "and follow these steps" what I think is fine. WDYT?
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nmirasch Minor suggestions from my side. Otherwise, your content looks good to me. Thank you! Very well written :)
...erlessworkflow/modules/ROOT/assets/images/use-cases/newsletter-subscription/architecture.png
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work!
...-cases/advanced-developer-use-cases/event-orchestration/newsletter-subscription-example.adoc
Outdated
Show resolved
Hide resolved
…oper-use-cases/event-orchestration/newsletter-subscription-example.adoc Co-authored-by: Ricardo Zanini <[email protected]>
Closes #557
How to backport a pull request to a different branch?
In order to automatically create a backporting pull request please add one or more labels having the following format
backport-<branch-name>
, where<branch-name>
is the name of the branch where the pull request must be backported to (e.g.,backport-7.67.x
to backport the original PR to the7.67.x
branch).Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.