spring-cloud / spring-cloud/spring-cloud-config
sparse checkout for spring config server
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
I dont know if it should be a bug or an enhancement, but when we are already telling config server to find configurations under a particular folder using following key :
spring.cloud.config.server.git.search-paths=
then why does config server checkout the entire git repository, and doesn't do sparse checkout of only that particular folder in the repository.
Because for my project it results in lack of performance when it tries to fetch the results as it has to see changes in entire project, which is very huge in my case. (don't forget the time taken by first time checkout )
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 Git-backed Config Server handling of spring.cloud.config.server.git.search-paths and trace how repositories are checked out and refreshed. Determine whether sparse checkout can limit work to the requested folder, and define done as fetching and checking only that path while preserving configuration lookup behavior and improving large-repository performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java, spring, spring-boot
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100