spring-projects / spring-projects/spring-boot
Provide support for registering functional web endpoints in the management context
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
See https://github.com/spring-projects/spring-boot/issues/31768 for background. We'd like to help people to move away from the WebMvc- and WebFlux-specific @RestControllerEndpoint and @ControllerEndpoint by making it easier to register functional web endpoints with Actuator. They would be automatically mapped beneath /actuator and move to the separate management server when it's running on a different port.
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 with the background in issue #31768 and compare the existing @RestControllerEndpoint and @ControllerEndpoint approaches. Define what support for functional web endpoints in Actuator must provide, including automatic /actuator mapping and placement on a separate management server when configured; completion should cover both behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100