From 10b8c018208d0113a1ed1a0d18c91cbbd4b01f85 Mon Sep 17 00:00:00 2001 From: Dave Syer Date: Mon, 25 Jan 2016 09:54:56 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- spring-cloud-config.html | 24 +++++++++++++++++++++++- 1 file changed, 23 insertions(+), 1 deletion(-) diff --git a/spring-cloud-config.html b/spring-cloud-config.html index 421e7ea6..258d8d83 100644 --- a/spring-cloud-config.html +++ b/spring-cloud-config.html @@ -1768,6 +1768,28 @@ default service id is "CONFIGSERVER" but you can change that on the client with spring.cloud.config.discovery.serviceId (and on the server in the usual way for a service, e.g. by setting spring.application.name).

+
+

The discovery client implementations all support some kind of metadata +map (e.g. for Eureka we have eureka.instance.metadataMap). Some +additional properties of the Config Server may need to be configured +in its service registration metadata so that clients can connect +correctly. If the Config Server is secured with HTTP Basic you can +configure the credentials as "username" and "password". And if the +Config Server has a context path you can set "configPath". Example, +for a Config Server that is a Eureka client:

+
+
+
bootstrap.yml
+
+
eureka:
+  instance:
+    ...
+    metadataMap:
+      username: osufhalskjrtl
+      password: lviuhlszvaorhvlo5847
+      configPath: /config
+
+

Config Client Fail Fast

@@ -1897,7 +1919,7 @@ grabbing it in the bootstrap context and injecting one).