Per User-limits Management Interface and HTTP API

Ayanda-D commented 4 years ago

Part of: https://github.com/rabbitmq/rabbitmq-server/pull/2380

This work has be carried out by Erlang Solutions and sponsored by CloudAMQP

Types of Changes

What types of changes does your code introduce to this project? Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes issue #NNNN)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (correction or otherwise)
[ ] Cosmetics (whitespace, appearance)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask on the mailing list. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING.md document
[x] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
[x] All tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in related repositories

Further Comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc.

michaelklishin commented 4 years ago

This has been merged manually with a merge commit. Keep this in mind when backporting.

michaelklishin commented 4 years ago

Follow-up changes: 5b8ca1ab, 74fbfbe6fcb449b141245ebfd2e4f4e5935e5a46.

michaelklishin commented 3 years ago

Backported to v3.8.x.

rabbitmq / rabbitmq-management