spring-projects / spring-projects/spring-boot
Allow config imports that aren't found to fail after the logging system is initialized
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-cloud/spring-cloud-config/issues/2051 for background.
Currently when a config import fails the processing is aborted. This means that logging configuration is ignored, even if it's in a part of the config data that loaded OK. It might be nice if we could fail after the logging system has been initialized so that logging is available.
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
No files or tests are named. Read the config-import failure flow and logging-system initialization path, using the linked Spring Cloud issue for context; determine how a missing import can fail after logging is initialized. Done means the requested ordering is implemented and covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100