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

Make it possible to set some node-specific metadata using tags #12702

Merged
merged 2 commits into from
Nov 11, 2024

Conversation

SimonUnge
Copy link
Member

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

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)
  • Build system and/or CI

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.

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • I have added tests that prove my fix is effective or that my feature works
  • All tests pass locally with my changes
  • If relevant, I have added necessary documentation to https://github.com/rabbitmq/rabbitmq-website
  • If relevant, I have added this change to the first version(s) in release-notes that I expect to introduce it

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 michaelklishin changed the title Node tags local to broker, add to /api/overview output and ctl status Make it possible to set some node-specific metadata using tags Nov 11, 2024
@SimonUnge SimonUnge marked this pull request as ready for review November 11, 2024 21:43
…eleased 4.0.x nodes

In a mixed cluster environment,
'rabbitmq-diagnostics status' can hit a node
that does not return any node tags.

Be more defensive and handle such cases
by simply displaying "(none)" for such
values.
@michaelklishin michaelklishin merged commit 859fd03 into main Nov 11, 2024
273 checks passed
@michaelklishin michaelklishin deleted the su_aws/node_tags branch November 11, 2024 23:34
@michaelklishin michaelklishin added this to the 4.1.0 milestone Nov 11, 2024
michaelklishin added a commit that referenced this pull request Nov 12, 2024
michaelklishin added a commit that referenced this pull request Nov 12, 2024
Make it possible to set some node-specific metadata using tags (backport #12702)
michaelklishin added a commit that referenced this pull request Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants