-
Notifications
You must be signed in to change notification settings - Fork 40.2k
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
Document that actuator over HTTP requires Jackson #19564
Comments
How can I take up this issue and work on it? |
Hi @ericus20, thanks for the offer of help. I think we really need an additional note in our Actuator API documentation that lets people know that they need to be using Jackson in order to get the correct JSON responses. I think the best place would be in the "Overview" section. If you're interested in adding that you can edit this file. It's written using asciidoctor markup which you can read about at https://asciidoctor.org/. |
@philwebb Thanks a lot. I will work on that then. |
@philwebb what about this documentation page? |
@Maxim-Nazarenko not sure that should be the reason to update this particular section. I was about to say that it might make sense in the overview for endpoints but it already has a link to the part Phil referenced:
@ericus20 any update about this documentation update? Do you need help? |
Yeah, I am on it and almost through. Just double-checking a couple of stuff before I present it for review. |
@ericus20 hello, are you still willing to work on this issue? |
@ericus20 given the lack of feedback, I am putting this one back to the pool. |
@Maxim-Nazarenko I don't think it does but I would need to spend a bit more time to know for sure. I know @bclozel has done some changes in that area so I'll check with him today. Thanks for the PR in any case! |
A customer reported an issue to the Apps Manager team that was due to changes in the actuator API. The status keys have a value that is an object like:
The root cause is this annotation not being respected if Jackson isn't being used.
The text was updated successfully, but these errors were encountered: