Support placeholders for searchPaths on remote repos
See original GitHub issueTo support a more flexible Git repo structure it would be good if the {placeholder} support was supported in the searchPaths option. Ideally we should be able to support having a single repo with config store under application (and profile) structure. Current implementation requires change to the searchPaths entry on the config server whenever a new application is added.
spring:
cloud:
config:
server:
git:
uri: https://xxxx/config-repo.git
searchPaths: {application}
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Spring Cloud Config Server
Spring Cloud Config Server supports a git repository URL with placeholders for the {application} and {profile} (and {label} if you need it, but...
Read more >Spring-cloud-config-server--environment Repository (Git backend)
Therefore, you can easily support the use of an "one repo" policy, for example: ... Placeholders in Git search paths--git the placeholder in...
Read more >Spring cloud config searchPaths vs repo directory structure
I'm trying to run Spring Cloud Config server (centralized-configuration-service) with remote repository on Git ...
Read more >Spring Cloud
Spring Cloud Config Server also supports a search path with placeholders for ... git: uri: https://github.com/spring-cloud-samples/config-repo searchPaths: ...
Read more >Externalizing Application Configuration With Spring Cloud ...
Here is a list of some of the supported backend. Git URL; AWS S3 bucket. ... Now, Let's create some configuration files, in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Works for me. You need to quote the search paths value in YAML (“{” is not a valid literal). Maybe that’s the problem?
I was also making same mistake, after quoting in doublesquotes it worked for me