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.

Sign up for GitHub

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

Jump to bottom

HTTP API: DELETE /api/queues/{vhost}/{name} should use an internal API call #8758

Closed
michaelklishin opened this issue Jul 4, 2023 · 1 comment
Closed

HTTP API: DELETE /api/queues/{vhost}/{name} should use an internal API call #8758

michaelklishin opened this issue Jul 4, 2023 · 1 comment
Assignees
@michaelklishin
Labels
usability
Milestone
3.12.7

Comments

@michaelklishin
Copy link
Member

Currently it uses a direct Erlang client operation, which would fail if the queue in question is exclusive.

On the contrary, rabbitmqctl delete_queue can delete exclusive queues just fine because it does
not use a client to do so.

There is no reason why the HTTP API should not use rabbit_amqqueue:delete/4 directly.
@michaelklishin michaelklishin self-assigned this Jul 4, 2023
@michaelklishin michaelklishin modified the milestone: 3.12.2 Jul 4, 2023
@dcorbacho dcorbacho mentioned this issue Sep 27, 2023
Merged
12 tasks
@michaelklishin michaelklishin added this to the 3.12.7 milestone Sep 27, 2023
@michaelklishin
Copy link
Member Author

This was reverted in #10185

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michaelklishin michaelklishin

Labels
usability
Projects
None yet
Milestone
3.12.7
Development

No branches or pull requests
1 participant
@michaelklishin