spring-cloud / spring-cloud/spring-cloud-config
Please add support for Spring Cloud Config to use Artifactory or similar maven repositories as a backing service
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
Several enterprises use Artifactory or a similar maven repository as the one and only source for all deployable artifacts. Further, artifacts representing configuration are also considered deployables and thus the artifact repository is considered the best source for housing them. The enhancement request is to allow Spring Cloud Config to then be pointed at the repository to source the config it provides to config clients.
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 surveying the Java Spring Cloud Config server and its current configuration backends, then define how an Artifactory-like Maven repository would be configured and accessed. Done means Spring Cloud Config can source client configuration from that repository with coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100