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

How to make tenant aware for multi tenant application? #68

Open
gwachhamit opened this issue Jun 22, 2022 · 3 comments
Open

How to make tenant aware for multi tenant application? #68

gwachhamit opened this issue Jun 22, 2022 · 3 comments

Comments

@gwachhamit
Copy link

How can we make this package and rabbitmq multi-tenant aware for multi-tenant application?

I am having a great problem implementing rabbitmq with this package for multi tenant application.

@KinaneD
Copy link
Member

KinaneD commented Jun 22, 2022

Hello @gwachhamit,
You should be looking into Rabbitmq Virtual Hosts.

For multi-tenant support, your application would need to register a new Connection instance per vHost.

@gwachhamit
Copy link
Author

gwachhamit commented Jun 23, 2022

@KinaneD I have create separate vHost per tenant. The problem is while consuming the message-event. Is there any way we can mention the rabbitmq credentials/vHost while consuming message-event.
Lets say for this package we have command php artisan bowler:consume example_queue can we pass any argument to specify rabbitmq credentials/vHost?

@KinaneD
Copy link
Member

KinaneD commented Jun 23, 2022

Hi @gwachhamit
I would really appreciate if you can share a scenario or a use case of what are your expectations.

You can get the Virtual Host of a Connection like so. The RabbitMQ setup and/or configuration are instance related not message specific.

I would like to loop in @cerpusoddarne into this thread, I hope he does not mind, since I believe he is more familiar than I am with the subject.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants