spring-projects / spring-projects/spring-boot
Allow ConfigDataLoader & EnvironmentPostProcessor to opt-out in AOT refreshed contexts
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
Preparing the Environment in a Spring Boot application have various forms depending on what's on the classpath. This can trigger HTTP calls to remote config server for instance. Wavefront also negotiates an API token if none is found.
In the latter case, it's obviously wrong to do that at build-time as the API token will not be used as we're evaluating conditions and not instantiating beans. Having the ability to know that the environment is prepared for an Ahead-of-time context optimization will allows those components to react accordingly.
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 tracing how ConfigDataLoader and EnvironmentPostProcessor participate in preparing the Environment for AOT-refreshed contexts. Define how those components can detect build-time evaluation, then verify that remote configuration calls and token negotiation are skipped there while normal runtime preparation remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- build-system, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100