From 8cf581d4964bc67d1d4fa3a89cff8e63aa02697c Mon Sep 17 00:00:00 2001 From: Dave Syer Date: Wed, 27 Jul 2016 11:37:14 +0100 Subject: [PATCH] Correct description of cloud foundry instance id Fixes gh-1214 --- docs/src/main/asciidoc/spring-cloud-netflix.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/src/main/asciidoc/spring-cloud-netflix.adoc b/docs/src/main/asciidoc/spring-cloud-netflix.adoc index 8cae580e..31b6d208 100644 --- a/docs/src/main/asciidoc/spring-cloud-netflix.adoc +++ b/docs/src/main/asciidoc/spring-cloud-netflix.adoc @@ -215,13 +215,13 @@ Using Spring Cloud you can override this by providing a unique identifier in `eu ---- eureka: instance: - instanceId: ${spring.application.name}:${spring.application.instance_id:${random.value}} + instanceId: ${spring.application.name}:${vcap.application.instance_id:${spring.application.instance_id:${random.value}}} ---- With this metadata, and multiple service instances deployed on localhost, the random value will kick in there to make the instance -unique. In Cloudfoundry the `spring.application.instance_id` will be -populated automatically in a Spring Boot Actuator application, so the +unique. In Cloudfoundry the `vcap.application.instance_id` will be +populated automatically in a Spring Boot application, so the random value will not be needed. === Using the EurekaClient