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

Are you using the RabbitMQ Broker? #746

Closed
salaboy opened this issue May 9, 2022 · 4 comments
Closed

Are you using the RabbitMQ Broker? #746

salaboy opened this issue May 9, 2022 · 4 comments
Labels
kind/feature-request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@salaboy
Copy link

salaboy commented May 9, 2022

If you are using Knative Eventing RabbitMQ Broker, we would love to know!

Why?

Tracking usage in OSS is hard, if you leave a comment on this issue we can better understand who our users are and deliver a better experience for YOU!

How can I help?

We'd like to give your organization the opportunity to collaborate more closely with contributors (if you want to)
We want to help promote your organization
We want to show off all the awesome stuff our users are doing
How you can help

Submit a comment in this issue to include the following information, which would then also get included in the [ADOPTERS.md]
(https://github.com/knative-sandbox/eventing-rabbitmq/blob/main/ADOPTERS.MD) file and (if applicable) on the Knative homepage:

Organization/Company: 
Website: 
Country: 
Contact: (email or Twitter at least one please!)
Usage scenario: e.g. We use Knative Eventing RabbitMQ Broker for XYZ
Status: Development?/Production?
@embano1
Copy link
Contributor

embano1 commented Aug 4, 2022

Organization/Company: VMware
Website: http://vmweventbroker.io
Country: USA
Contact: dl-veba@vmware.com
Usage scenario: We use Knative Eventing RabbitMQ Broker as the backend for the appliance to build event-driven integrations
Status: Development (VEBA is a community-supported VMware Fling)

@github-actions
Copy link

github-actions bot commented Nov 3, 2022

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 3, 2022
@knative-prow-robot
Copy link

This issue or pull request is stale because it has been open for 90 days with no activity.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close

/lifecycle stale

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 4, 2022
@github-actions
Copy link

github-actions bot commented Mar 4, 2023

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 4, 2023
@github-actions github-actions bot closed this as completed Apr 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature-request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants