Sync docs from master to gh-pages
This commit is contained in:
@@ -536,6 +536,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
|
||||
<ul class="sectlevel2">
|
||||
<li><a href="#netflix-zuul-reverse-proxy">Embedded Zuul Reverse Proxy</a></li>
|
||||
<li><a href="#_cookies_and_sensitive_headers">Cookies and Sensitive Headers</a></li>
|
||||
<li><a href="#_the_routes_endpoint">The Routes Endpoint</a></li>
|
||||
<li><a href="#_strangulation_patterns_and_local_forwards">Strangulation Patterns and Local Forwards</a></li>
|
||||
<li><a href="#_uploading_files_through_zuul">Uploading Files through Zuul</a></li>
|
||||
<li><a href="#_plain_embedded_zuul">Plain Embedded Zuul</a></li>
|
||||
@@ -578,7 +579,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
|
||||
<li><a href="#_binder_spi">Binder SPI</a></li>
|
||||
<li><a href="#_binder_detection">Binder Detection</a></li>
|
||||
<li><a href="#multiple-binders">Multiple Binders on the Classpath</a></li>
|
||||
<li><a href="#_connecting_to_multiple_systems">Connecting to Multiple Systems</a></li>
|
||||
<li><a href="#multiple-systems">Connecting to Multiple Systems</a></li>
|
||||
<li><a href="#_binder_configuration_properties">Binder configuration properties</a></li>
|
||||
<li><a href="#_implementation_strategies">Implementation strategies</a></li>
|
||||
</ul>
|
||||
@@ -1506,7 +1507,7 @@ users. Example Maven configuration:</p>
|
||||
<pre class="highlight"><code class="language-xml" data-lang="xml"><parent>
|
||||
<groupId>org.springframework.boot</groupId>
|
||||
<artifactId>spring-boot-starter-parent</artifactId>
|
||||
<version>1.2.3.RELEASE</version>
|
||||
<version>1.3.5.RELEASE</version>
|
||||
<relativePath /> <!-- lookup parent from repository -->
|
||||
</parent>
|
||||
|
||||
@@ -1514,8 +1515,8 @@ users. Example Maven configuration:</p>
|
||||
<dependencies>
|
||||
<dependency>
|
||||
<groupId>org.springframework.cloud</groupId>
|
||||
<artifactId>spring-cloud-starter-parent</artifactId>
|
||||
<version>1.0.1.RELEASE</version>
|
||||
<artifactId>spring-cloud-dependencies</artifactId>
|
||||
<version>Brixton.RELEASE</version>
|
||||
<type>pom</type>
|
||||
<scope>import</scope>
|
||||
</dependency>
|
||||
@@ -1741,7 +1742,7 @@ Server? The strategy that governs this behaviour is the
|
||||
<p><code>{application}</code> maps to "spring.application.name" on the client side;</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>{profile}</code> maps to "spring.active.profiles" on the client (comma separated list); and</p>
|
||||
<p><code>{profile}</code> maps to "spring.profiles.active" on the client (comma separated list); and</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>{label}</code> which is a server side feature labelling a "versioned" set of config files.</p>
|
||||
@@ -3402,22 +3403,22 @@ normal Eureka functionality under <code>/eureka/*</code>.</p>
|
||||
</td>
|
||||
<td class="content">
|
||||
<div class="paragraph">
|
||||
<p>Due to Gradle’s dependency resolution rules and the lack of a parent bom feature, simply depending on spring-cloud-starter-eureka-server can cause failures on application startup. To remedy this the Spring dependency management plugin must be added and the Spring cloud starter parent bom must be imported like so:</p>
|
||||
<p>Due to Gradle’s dependency resolution rules and the lack of a parent bom feature, simply depending on spring-cloud-starter-eureka-server can cause failures on application startup. To remedy this the Spring Boot Gradle plugin must be added and the Spring cloud starter parent bom must be imported like so:</p>
|
||||
</div>
|
||||
<div class="listingblock">
|
||||
<div class="title">build.gradle</div>
|
||||
<div class="content">
|
||||
<pre class="highlight"><code class="language-java" data-lang="java">buildscript {
|
||||
dependencies {
|
||||
classpath "io.spring.gradle:dependency-management-plugin:0.4.0.RELEASE"
|
||||
classpath("org.springframework.boot:spring-boot-gradle-plugin:1.3.5.RELEASE")
|
||||
}
|
||||
}
|
||||
|
||||
apply plugin: "io.spring.dependency-management"
|
||||
apply plugin: "spring-boot"
|
||||
|
||||
dependencyManagement {
|
||||
imports {
|
||||
mavenBom 'org.springframework.cloud:spring-cloud-starter-parent:1.0.0.RELEASE'
|
||||
mavenBom "org.springframework.cloud:spring-cloud-dependencies:Brixton.RELEASE"
|
||||
}
|
||||
}</code></pre>
|
||||
</div>
|
||||
@@ -3708,18 +3709,30 @@ for details on the properties available.</p>
|
||||
<p>In this case, the cluster name from 4 services is pulled from their metadata map, and is expected to have values that include "SYSTEM" and "USER".</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>To use the "default" cluster for all apps you need a string literal expression (with single quotes):</p>
|
||||
<p>To use the "default" cluster for all apps you need a string literal expression (with single quotes, and escaped with double quotes if it is in YAML as well):</p>
|
||||
</div>
|
||||
<div class="listingblock">
|
||||
<div class="content">
|
||||
<pre>turbine:
|
||||
appConfig: customers,stores
|
||||
clusterNameExpression: 'default'</pre>
|
||||
clusterNameExpression: "'default'"</pre>
|
||||
</div>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>Spring Cloud provides a <code>spring-cloud-starter-turbine</code> that has all the dependencies you need to get a Turbine server running. Just create a Spring Boot application and annotate it with <code>@EnableTurbine</code>.</p>
|
||||
</div>
|
||||
<div class="admonitionblock note">
|
||||
<table>
|
||||
<tr>
|
||||
<td class="icon">
|
||||
<div class="title">Note</div>
|
||||
</td>
|
||||
<td class="content">
|
||||
by default the native Netflix behaviour built into Turbine does <em>not</em> allow multiple processes per host, per cluster (the key to the instance id is the hostname). Spring Cloud generalizes this a bit, allowing the host and port to be used as the key, but only if you set the property <code>turbine.combineHostPort=true</code>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sect2">
|
||||
<h3 id="_turbine_stream">Turbine Stream</h3>
|
||||
@@ -4507,7 +4520,7 @@ level, but "/myusers/**" matches hierarchically.</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>The location of the backend can be specified as either a "serviceId"
|
||||
(for a Eureka service) or a "url" (for a physical location), e.g.</p>
|
||||
(for a service from discovery) or a "url" (for a physical location), e.g.</p>
|
||||
</div>
|
||||
<div class="listingblock">
|
||||
<div class="title">application.yml</div>
|
||||
@@ -4700,6 +4713,30 @@ might add these headers too, and we want the values from the proxy.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sect2">
|
||||
<h3 id="_the_routes_endpoint">The Routes Endpoint</h3>
|
||||
<div class="paragraph">
|
||||
<p>If you are using <code>@EnableZuulProxy</code> with tha Spring Boot Actuator you
|
||||
will enable (by default) an additional endpoint, available via HTTP as
|
||||
<code>/routes</code>. A GET to this endpoint will return a list of the mapped
|
||||
routes. A POST will force a refresh of the existing routes (e.g. in
|
||||
case there have been changes in the service catalog).</p>
|
||||
</div>
|
||||
<div class="admonitionblock note">
|
||||
<table>
|
||||
<tr>
|
||||
<td class="icon">
|
||||
<div class="title">Note</div>
|
||||
</td>
|
||||
<td class="content">
|
||||
the routes should respond automatically to changes in the
|
||||
service catalog, but the POST to /routes is a way to force the change
|
||||
to happen immediately.
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sect2">
|
||||
<h3 id="_strangulation_patterns_and_local_forwards">Strangulation Patterns and Local Forwards</h3>
|
||||
<div class="paragraph">
|
||||
<p>A common pattern when migrating an existing application or API is to
|
||||
@@ -6298,7 +6335,7 @@ spring.cloud.stream.bindings.output.binder=rabbit</pre>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sect2">
|
||||
<h3 id="_connecting_to_multiple_systems">Connecting to Multiple Systems</h3>
|
||||
<h3 id="multiple-systems">Connecting to Multiple Systems</h3>
|
||||
<div class="paragraph">
|
||||
<p>By default, binders share the application’s Spring Boot auto-configuration, so that one instance of each binder found on the classpath will be created.
|
||||
If your application should connect to more than one broker of the same type, you can specify multiple binder configurations, each with different environment settings.</p>
|
||||
@@ -6472,6 +6509,19 @@ If set, only listed destinations can be bound.</p>
|
||||
<dd>
|
||||
<p> The default binder to use, if multiple binders are configured.
|
||||
See <a href="#multiple-binders">Multiple Binders on the Classpath</a>.</p>
|
||||
<div class="paragraph">
|
||||
<p>Default: empty.</p>
|
||||
</div>
|
||||
</dd>
|
||||
<dt class="hdlist1">spring.cloud.stream.overrideCloudConnectors</dt>
|
||||
<dd>
|
||||
<p> This property is only applicable when the <code>cloud</code> profile is active and Spring Cloud Connectors are provided with the application.
|
||||
If the property is false (the default), the binder will detect a suitable bound service (e.g. a RabbitMQ service bound in Cloud Foundry for the RabbitMQ binder) and will use it for creating connections (usually via Spring Cloud Connectors).
|
||||
When set to true, this property instructs binders to completely ignore the bound services and rely on Spring Boot properties (e.g. relying on the <code>spring.rabbitmq.*</code> properties provided in the environment for the RabbitMQ binder).
|
||||
The typical usage of this property is to be nested in a customized environment <a href="#multiple-systems">when connecting to multiple systems</a>.</p>
|
||||
<div class="paragraph">
|
||||
<p>Default: false.</p>
|
||||
</div>
|
||||
</dd>
|
||||
</dl>
|
||||
</div>
|
||||
@@ -13024,7 +13074,7 @@ created during auto-configuration.</p>
|
||||
</div>
|
||||
<div id="footer">
|
||||
<div id="footer-text">
|
||||
Last updated 2016-06-04 08:17:48 UTC
|
||||
Last updated 2016-05-18 09:45:16 +01:00
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
Reference in New Issue
Block a user