-
Notifications
You must be signed in to change notification settings - Fork 41.4k
Remove management.health.status.order from docs #18170
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
Remove management.health.status.order from docs #18170
Conversation
@philwebb I just noticed another slightly related doc error related to this. Give me a minute to fix this. |
Sure thing! I'm just triaging issues at the moment, not merging. |
Done. |
@@ -162,7 +171,10 @@ | |||
"OUT_OF_SERVICE", | |||
"UP", | |||
"UNKNOWN" | |||
] | |||
], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This shouldn't be required as the annotation processor is supposed to pick things up. I've opened #18184
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The issue is fixed so I'll rebase and polish this part.
Hi,
while working on another PR I noticed that
management.health.status.order
is still showing in the Actuator Properties section of the docs, although it should be deprecated.This PR also fixes
management.endpoint.health.status.http-mapping.*
not showing up at all as a side-effect.Let me know what you think. I found it quite "unintuitive" - maybe that's the word I'm looking for - to work with the metadata stuff and I'm not sure if this should be solved differently or if there is a convention for the metadata.json files.
Cheers,
Christoph