triggermesh
triggermesh copied to clipboard
triggermesh
THIS PROJECT HAS CLOSED DOWN
What's happened seems like one minute I'm looking at docs next min I'm debating using this at all.
Due to lack of traction/adoption the company shutdown last fall. The team that started this project is not working on it anymore. We left it open as open source, but it is not maintained.
@sebgoa are you able to consider handing this over to someone to maintain it going forward? I will put my hand up to restart it and take MRs and do releases, and accept extra contributors.
you can fork at will, it is all Apache License.
Just reach out to me via email [email protected] I am not on Slack anymore
OK, so you would prefer a fork rather than taking over ownership of this repo then?
Would be willing to help maintain if there is more interest from others too
@richardvflux let's talk live, ping me at [email protected] it will be easier and we can find a path forward.
It's a shame that such an interesting project has closed.
Can you think of any open source alternatives that could fill the void left by this project?
Is there a company that could take over?
Many thanks to the whole triggermesh team for launching something like this.
what about knative-eventing? is it comparable to triggermesh?
Triggermesh is using knative eventing under the hood.
@richardvflux @sebgoa were you able to find a path forward. Would like to know if this will be maintained or is there any fork that would take the baton?
Hi Mukund, I replied to you by email.
This project can totally be forked and used since it is ASL v2. But triggermesh in particular will not be maintained going forward.
If you have a need for consulting please reach out by email.
I will soon archive the project all together.
-Sebastien
Is there any way to get gcr.io/triggermesh/triggermesh-controller:v1.27.0 and the other images? Somebody saved them?
In Knative Eventing, we're adding more sources and sinks, we would be interested in knowing what sources and sinks you're using so that we can prioritize them and we would welcome additional maintainers, feel free to leave a comment here https://github.com/knative/eventing/issues/8185
We would love to hear from you in regards to the interest. OpenShift Serverless Red Hat is looking into offering more with the offering. Please follow @pierDipi comment for joining the conversation and helping us move eventing forward in this direction
@pierDipi we only use the AWSEventBridgeSource to get all S3 events into our Knative-Eventing stack. In the end Triggermesh created the AWS SQS and created an EventBus rule (within AWS Eventbridge) to feed all S3 events into that SQS. Then, the source forwards all SQS messages into the Knative Broker.
TriggerMesh provided a very good abstraction.
A simple AWS SQS source would be enough for us too.