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

Following same URL approach than InMemory Broker and Kafka Broker #585

Closed
salaboy opened this issue Jan 24, 2022 · 1 comment · Fixed by #587
Closed

Following same URL approach than InMemory Broker and Kafka Broker #585

salaboy opened this issue Jan 24, 2022 · 1 comment · Fixed by #587

Comments

@salaboy
Copy link

salaboy commented Jan 24, 2022

Problem

The url format for the InMemory and Kafka BRoker follow the pattern of: http://<broker-URL>/<namespace>/<broker-name>
I think we should align with this format, even if our brokers are not multi-tenant, as discussed in our weekly sync.
By following the same pattern we will reduce friction from people moving from the InMemory Broker or the Kafka Broker to RabbitMQ

Persona:

System Integrator, System Operator or Developer creating a broker

Exit Criteria

When a broker is created the URL exposed follow the pattern: /<namespace>/<broker-name>

Time Estimate (optional):
(TBD)

Additional context (optional)

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

Successfully merging a pull request may close this issue.

3 participants