spring:
+ cloud:
+ config:
+ server:
+ git:
+ uri: https://github.com/spring-cloud-samples/config-repo
+ force-pull: true
+diff --git a/spring-cloud-config.html b/spring-cloud-config.html index 277672e8..6935f8ae 100644 --- a/spring-cloud-config.html +++ b/spring-cloud-config.html @@ -1121,6 +1121,70 @@ path with placeholders (any matching directory is included in the search).
+As mentioned before Spring Cloud Config Server makes a clone of the +remote git repository and if somehow the local copy gets dirty (e.g. +folder content changes by OS process) so Spring Cloud Config Server +cannot update the local copy from remote repository.
+To solve this there is a force-pull property that will make Spring Cloud
+Config Server force pull from remote repository if the local copy is dirty.
+Example:
spring:
+ cloud:
+ config:
+ server:
+ git:
+ uri: https://github.com/spring-cloud-samples/config-repo
+ force-pull: true
+If you have a multiple repositories configuration you can configure the
+force-pull property per repository. Example:
spring:
+ cloud:
+ config:
+ server:
+ git:
+ uri: https://git/common/config-repo.git
+ force-pull: true
+ repos:
+ team-a:
+ pattern: team-a-*
+ uri: http://git/team-a/config-repo.git
+ force-pull: true
+ team-b:
+ pattern: team-b-*
+ uri: http://git/team-b/config-repo.git
+ force-pull: true
+ team-c:
+ pattern: team-c-*
+ uri: http://git/team-a/config-repo.git
+|
+ Note
+ |
+
+The default value for force-pull property is false.
+ |
+