spring-cloud / spring-cloud/spring-cloud-config
Applying common configuration to app level configuration or any feasibility
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
Problem Statement:
We have many micro services with their own app level configuration in repos but the configuration is duplicated across all the app level repos. If we need to change anything like a connection then we are doing it in multiple places.
Possible Solution:
Is there a possibility to apply common configuration from one repo to app level specific repo? Or any workarounds to our current problem?
We want to transition from current folder and repo level to either Transition V1 or Transition V2 as depicted below.
PS - everybox is a folder unless mentioned as repo
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
The issue names no files, tests, or entry points. Start by reviewing the repository's configuration model and the Transition V1/V2 diagram, then determine whether shared app-level configuration is supported or feasible. Done requires an agreed approach or documented feasibility result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java, spring, spring-boot
- Domain
- backend, cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100