The bootstrap.yml (or .properties) location can be specified using
-spring.cloud.bootstrap.name (default "bootstrap") or
+
The bootstrap.yml (or .properties) location can be specified using
+`spring.cloud.bootstrap.name (default "bootstrap") or
spring.cloud.bootstrap.location (default empty), e.g. in System
properties. Those properties behave like the spring.config.*
variants with the same name, in fact they are used to set up the
@@ -1236,7 +1236,7 @@ high-priority property source, e.g.
$ curl localhost:8080/env
{
"profiles":[],
- "configService:https://github.com/scratches/config-repo/bar.properties":{"foo":"bar"},
+ "configService:https://github.com/spring-cloud-samples/config-repo/bar.properties":{"foo":"bar"},
"servletContextInitParams":{},
"systemProperties":{...},
...
@@ -1248,6 +1248,19 @@ high-priority property source, e.g.
repository>/<file name>" contains the property "foo" with value
"bar" and is highest priority).
|
+ Note
+ |
++the URL in the property source name is the git repository not +the config server URL. + | +
The Config Service serves property sources from /{name}/{env}/{label}, where the default bindings in the client app are
The Config Service serves property sources from /{name}/{profile}/{label}, where the default bindings in the client app are
"name" = ${spring.application.name}
"env" = ${spring.profiles.active} (actually Environment.getActiveProfiles())
"profile" = ${spring.profiles.active} (actually Environment.getActiveProfiles())
"label" = "master"
@@ -1893,7 +1906,7 @@ an Exception.All of them can be overridden by setting spring.cloud.config.*
-(where * is "name", "env" or "label"). The "label" is useful for
+(where * is "name", "profile" or "label"). The "label" is useful for
rolling back to previous versions of configuration; with the default
Config Server implementation it can be a git label, branch name or
commit id. Label can also be provided as a comma-separated list, in
@@ -2102,6 +2115,24 @@ application, so it’s helpful if they are accurate.
If the application is planned to be deployed to an AWS cloud, then the Eureka instance will have to be configured to be Amazon aware and this can be done by customizing the EurekaInstanceConfigBean the following way:
+@Bean
+@Profile("!default")
+public EurekaInstanceConfigBean eurekaInstanceConfig() {
+ EurekaInstanceConfigBean b = new EurekaInstanceConfigBean();
+ AmazonInfo info = AmazonInfo.Builder.newBuilder().autoBuild("eureka");
+ b.setDataCenterInfo(info);
+ return b;
+}By default a eureka instance is registered with an ID that is equal to its host name (i.e. only one service per host). Using Spring Cloud you can override this by providing a unique identifier in eureka.instance.metadataMap.instanceId. For example: