SpringCloud/spring-cloud-config
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Make it explicit that an optional prefix is needed for discovery first. Fixes #1897

Browse Source
This commit is contained in:
Ryan Baxter
2021-06-02 12:36:40 -04:00
committed by GitHub
parent 01f4d4785f
commit b1e795d8d1
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/src/main/asciidoc/spring-cloud-config.adoc
View File

@@ -1514,7 +1514,7 @@ The net result of this behavior is that all client applications that want to con
[[discovery-first-bootstrap]]
==== Discovery First Lookup
WARNING: Unless you are using <<config-first-bootstrap, config first bootstrap>>, you will need to have a `spring.config.import` property in your configuration properties.
WARNING: Unless you are using <<config-first-bootstrap, config first bootstrap>>, you will need to have a `spring.config.import` property in your configuration properties with an `optional:` prefix.
For example, `spring.config.import=optional:configserver:`.
If you use a `DiscoveryClient` implementation, such as Spring Cloud Netflix and Eureka Service Discovery or Spring Cloud Consul, you can have the Config Server register with the Discovery Service.