rabbitmq / rabbitmq-server

Open source RabbitMQ: core server and tier 1 (built-in) plugins
https://www.rabbitmq.com/
Other
12.31k stars 3.92k forks source link

Make it possible to set some node-specific metadata using tags (backport #12702) #12703

Closed mergify[bot] closed 1 week ago

mergify[bot] commented 1 week ago

Similar to #12699 but node specific.

Proposed Changes

Config node tags in config file. Store as application setting and expose them via /api/overview and rabbitmqctl status command.

Types of Changes

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

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.

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.


This is an automatic backport of pull request #12702 done by Mergify.

mergify[bot] commented 1 week ago

Cherry-pick of 3d35416635cc4567f2da8f07095eadd7e70155de has failed:

On branch mergify/bp/v4.0.x/pr-12702
Your branch is up to date with 'origin/v4.0.x'.

You are currently cherry-picking commit 3d35416635.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
    modified:   deps/rabbit/priv/schema/rabbit.schema
    modified:   deps/rabbit/src/rabbit.erl
    modified:   deps/rabbitmq_cli/lib/rabbitmq/cli/ctl/commands/status_command.ex
    modified:   deps/rabbitmq_management/src/rabbit_mgmt_wm_overview.erl

Unmerged paths:
  (use "git add <file>..." to mark resolution)
    both modified:   deps/rabbitmq_management/test/rabbit_mgmt_http_SUITE.erl

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally