Many source code repository providers (like Github, Gitlab or Bitbucket +
Many source code repository providers (like Github, Gitlab, Gitee or Bitbucket
for instance) will notify you of changes in a repository through a
webhook. You can configure the webhook via the provider’s user
interface as a URL and a set of events in which you are
@@ -18,8 +18,8 @@ name (e.g. "foo.properties" is targeted at the "foo" application, and
"application.properties" is targeted at all applications). The strategy
if you want to override the behaviour is PropertyPathNotificationExtractor
which accepts the request headers and body as parameters and returns a list
-of file paths that changed.
The default configuration works out of the box with Github, Gitlab or -Bitbucket. In addition to the JSON notifications from Github, Gitlab +of file paths that changed.
The default configuration works out of the box with Github, Gitlab, Gitee or
+Bitbucket. In addition to the JSON notifications from Github, Gitlab, Gitee
or Bitbucket you can trigger a change notification by POSTing to
"/monitor" with a form-encoded body parameters path={name}. This will
broadcast to applications matching the "{name}" pattern (can contain
diff --git a/single/spring-cloud-config.html b/single/spring-cloud-config.html
index 12be03fe..30b820d9 100644
--- a/single/spring-cloud-config.html
+++ b/single/spring-cloud-config.html
@@ -761,7 +761,7 @@ resources under a prefix. The prefix should start but not end with a
the backend repository (instead of from the config server) that’s
basically an embedded config server with no endpoints. You can switch
off the endpoints entirely if you don’t use the @EnableConfigServer
-annotation (just set spring.cloud.config.server.bootstrap=true).
Many source code repository providers (like Github, Gitlab or Bitbucket
+annotation (just set spring.cloud.config.server.bootstrap=true).
Many source code repository providers (like Github, Gitlab, Gitee or Bitbucket
for instance) will notify you of changes in a repository through a
webhook. You can configure the webhook via the provider’s user
interface as a URL and a set of events in which you are
@@ -779,8 +779,8 @@ name (e.g. "foo.properties" is targeted at the "foo" application, and
"application.properties" is targeted at all applications). The strategy
if you want to override the behaviour is PropertyPathNotificationExtractor
which accepts the request headers and body as parameters and returns a list
-of file paths that changed.
The default configuration works out of the box with Github, Gitlab or -Bitbucket. In addition to the JSON notifications from Github, Gitlab +of file paths that changed.
The default configuration works out of the box with Github, Gitlab, Gitee or
+Bitbucket. In addition to the JSON notifications from Github, Gitlab, Gitee
or Bitbucket you can trigger a change notification by POSTing to
"/monitor" with a form-encoded body parameters path={name}. This will
broadcast to applications matching the "{name}" pattern (can contain
diff --git a/spring-cloud-config.xml b/spring-cloud-config.xml
index 8c0012d7..d20b0ce2 100644
--- a/spring-cloud-config.xml
+++ b/spring-cloud-config.xml
@@ -1233,7 +1233,7 @@ annotation (just set