Skip to content

Conversation

@michaelklishin
Copy link
Collaborator

This legacy health check has been deprecated since 2019 with a group of alternatives available.

Closes #3892, supersedes (rebases) #3893.

Closes #3892

(cherry picked from commit 66e92c3)

Conflicts:
	deps/rabbit/src/rabbit_health_check.erl
Copy link
Collaborator

@lukebakken lukebakken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about exiting with status 64 EX_USAGE? That would force people to take notice.

@michaelklishin
Copy link
Collaborator Author

I intentionally tried to not break anything. But now that it was suggested for 4.0, I guess we can do that.

@lukebakken lukebakken added this to the 4.0.0 milestone Mar 21, 2022
@michaelklishin
Copy link
Collaborator Author

I have forgotten about this PR and submitted #9982 for 3.13, haha.

@michaelklishin michaelklishin deleted the rabbitmq-server-3892-take-2 branch November 23, 2023 23:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make legacy node health check (rabbitmq-diagnostics node_health_check) a no-op

3 participants