Skip to content
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

Migrating Kogito Eventing Source to Knative Sandbox #1

Merged

Conversation

ricardozanini
Copy link
Member

Signed-off-by: Ricardo Zanini zanini@redhat.com

Changes

Initial migration of the Knative Eventing Kogito to Sandbox.

  • 🎁 Deploy a Kogito Service Event source
  • 🎁 Ability to describe any addressable sink to a deployed Kogito Service

/kind enhancement

Fixes #

Release Note

Introduce the Knative Eventing Kogito Source. Now Kogito users can leverage the Knative Eventing platform to manage events produced by any Kogito service. See the [examples](https://github.com/knative-sandbox/eventing-kogito/tree/migrate-repo/examples) to know how to start orchestrating events on Knative Eventing platform with Kogito.

Docs


Documentation will be updated in the next couple of days.

Signed-off-by: Ricardo Zanini <zanini@redhat.com>
@knative-prow-robot
Copy link

@ricardozanini: The label(s) kind/enhancement cannot be applied, because the repository doesn't have them.

In response to this:

Signed-off-by: Ricardo Zanini zanini@redhat.com

Changes

Initial migration of the Knative Eventing Kogito to Sandbox.

  • 🎁 Deploy a Kogito Service Event source
  • 🎁 Ability to describe any addressable sink to a deployed Kogito Service

/kind enhancement

Fixes #

Release Note

Introduce the Knative Eventing Kogito Source. Now Kogito users can leverage the Knative Eventing platform to manage events produced by any Kogito service. See the [examples](https://github.com/knative-sandbox/eventing-kogito/tree/migrate-repo/examples) to know how to start orchestrating events on Knative Eventing platform with Kogito.

Docs


Documentation will be updated in the next couple of days.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@google-cla google-cla bot added the cla: yes Indicates the PR's author has signed the CLA. label Aug 25, 2021
@knative-prow-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ricardozanini

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Aug 25, 2021
@ricardozanini ricardozanini self-assigned this Aug 25, 2021
@ricardozanini
Copy link
Member Author

cc @lionelvillard

@lionelvillard
Copy link
Contributor

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 25, 2021
@knative-prow-robot knative-prow-robot merged commit c4fdc8a into knative-extensions:main Aug 25, 2021
@ricardozanini ricardozanini deleted the migrate-repo branch August 25, 2021 18:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants