spring-projects / spring-projects/spring-boot
Environment Report when running with -Ddebug=true
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
Similar to the autoconfig report, it would be very helpful to print the output of the Environment actuator when the debug flag is set.
This would help to debug failures related to invalid or missing properties, particularly in a setup where properties come from dynamic sources such as the Spring Cloud Config Server.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing how the debug flag triggers the autoconfig report with how the Environment actuator produces its output. Trace the relevant Spring Boot entry points and tests, then verify that enabling -Ddebug=true includes the Environment report and that the output helps diagnose missing or invalid properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100