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

Spring Boot 3 Actuator indentation not working #34000

Closed
TrinhChuong opened this issue Jan 27, 2023 · 1 comment
Closed

Spring Boot 3 Actuator indentation not working #34000

TrinhChuong opened this issue Jan 27, 2023 · 1 comment
Labels
status: invalid An issue that we don't feel is valid

Comments

@TrinhChuong
Copy link

Created a new Spring Initializer java 17 gradle project in IntelliJ using Spring Boot version 3.0.2.
Included Spring Web and Spring Boot Actuator.

Did the same using Spring Boot version 2.7.8.

Both projects have the following in application.properties

management.endpoints.web.exposure.include=info
management.info.build.enabled=true
spring.jackson.serialization.indent-output=true

When requesting /actuator/info for version 3.0.2 project, the JSON is not indented or pretty printed. The same request for version 2.7.8 project returns pretty printed and indented JSON.

Everything is left default, no code additions, config changes. etc. Just plain vanilla out of the box project.

Is this a bug in Spring Boot version 3?

Expected the JSON response to be pretty printed and indented as per the Spring documentation for the Application Properties settings.

This is also posted in Stackoverflow (https://stackoverflow.com/questions/75221023/spring-boot-3-actuator-indentation-not-working). Seems there are other experiencing the same behaviour.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jan 27, 2023
@bclozel
Copy link
Member

bclozel commented Jan 27, 2023

This has been done on purpose in #20291 and is also documented in the migration guide.

I'm closing this issue as a result. Let us know if the migration guide is missing information on how to work things out on your side. Thanks!

@bclozel bclozel closed this as not planned Won't fix, can't repro, duplicate, stale Jan 27, 2023
@bclozel bclozel added status: invalid An issue that we don't feel is valid and removed status: waiting-for-triage An issue we've not yet triaged labels Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

3 participants