From 4fc9696060b8306c1a4a0ab7c1dae73d4eaf3151 Mon Sep 17 00:00:00 2001 From: Eugene Date: Sat, 20 Mar 2021 14:23:13 -0400 Subject: [PATCH] Updates case of property in documentation Fixes gh-1840 --- docs/src/main/asciidoc/spring-cloud-config.adoc | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/src/main/asciidoc/spring-cloud-config.adoc b/docs/src/main/asciidoc/spring-cloud-config.adoc index 0de707b9..302cccd1 100644 --- a/docs/src/main/asciidoc/spring-cloud-config.adoc +++ b/docs/src/main/asciidoc/spring-cloud-config.adoc @@ -241,7 +241,7 @@ spring: NOTE: Spring Cloud guesses that a pattern containing a profile that does not end in `\*` implies that you actually want to match a list of profiles starting with this pattern (so `*/staging` is a shortcut for `["\*/staging", "*/staging,*"]`, and so on). This is common where, for instance, you need to run applications in the "`development`" profile locally but also the "`cloud`" profile remotely. -Every repository can also optionally store config files in sub-directories, and patterns to search for those directories can be specified as `searchPaths`. +Every repository can also optionally store config files in sub-directories, and patterns to search for those directories can be specified as `search-paths`. The following example shows a config file at the top level: [source,yaml] @@ -252,7 +252,9 @@ spring: server: git: uri: https://github.com/spring-cloud-samples/config-repo - searchPaths: foo,bar* + search-paths: + - foo + - bar* ---- In the preceding example, the server searches for config files in the top level and in the `foo/` sub-directory and also any sub-directory whose name begins with `bar`. @@ -448,7 +450,7 @@ spring: server: git: uri: https://github.com/spring-cloud-samples/config-repo - searchPaths: '{application}' + search-paths: '{application}' ---- The preceding listing causes a search of the repository for files in the same name as the directory (as well as the top level).