diff --git a/Dalston.SR4/multi/multi__client_side_usage_2.html b/Dalston.SR4/multi/multi__client_side_usage_2.html index d9d6fc52..38327aaa 100644 --- a/Dalston.SR4/multi/multi__client_side_usage_2.html +++ b/Dalston.SR4/multi/multi__client_side_usage_2.html @@ -13,7 +13,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> diff --git a/Dalston.SR4/multi/multi__spring_cloud_config.html b/Dalston.SR4/multi/multi__spring_cloud_config.html index de19730e..1f51e92c 100644 --- a/Dalston.SR4/multi/multi__spring_cloud_config.html +++ b/Dalston.SR4/multi/multi__spring_cloud_config.html @@ -1,3 +1,3 @@ - Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file + Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

Dalston.SR4

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file diff --git a/Dalston.SR4/multi/multi__spring_cloud_consul.html b/Dalston.SR4/multi/multi__spring_cloud_consul.html index d69d2ee2..a89d2421 100644 --- a/Dalston.SR4/multi/multi__spring_cloud_consul.html +++ b/Dalston.SR4/multi/multi__spring_cloud_consul.html @@ -1,6 +1,6 @@ - Part VIII. Spring Cloud Consul
Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration + Part VIII. Spring Cloud Consul

Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

Dalston.SR4

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The diff --git a/Dalston.SR4/multi/multi__spring_cloud_contract.html b/Dalston.SR4/multi/multi__spring_cloud_contract.html index a10ed152..c868369f 100644 --- a/Dalston.SR4/multi/multi__spring_cloud_contract.html +++ b/Dalston.SR4/multi/multi__spring_cloud_contract.html @@ -1,4 +1,4 @@ Part XII. Spring Cloud Contract

Part XII. Spring Cloud Contract
Prev   Next

Part XII. Spring Cloud Contract

Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer

1.3.5.BUILD-SNAPSHOT

Prev   Next
77. Single Sign On Home 78. Spring Cloud Contract
\ No newline at end of file +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer

Dalston.SR4

Prev   Next
77. Single Sign On Home 78. Spring Cloud Contract
\ No newline at end of file diff --git a/Dalston.SR4/multi/multi__spring_cloud_netflix.html b/Dalston.SR4/multi/multi__spring_cloud_netflix.html index 874cb141..67dae09b 100644 --- a/Dalston.SR4/multi/multi__spring_cloud_netflix.html +++ b/Dalston.SR4/multi/multi__spring_cloud_netflix.html @@ -1,6 +1,6 @@ - Part III. Spring Cloud Netflix
Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration + Part III. Spring Cloud Netflix

Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

Dalston.SR4

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The diff --git a/Dalston.SR4/multi/multi__spring_cloud_sleuth.html b/Dalston.SR4/multi/multi__spring_cloud_sleuth.html index cd824b23..b09224bc 100644 --- a/Dalston.SR4/multi/multi__spring_cloud_sleuth.html +++ b/Dalston.SR4/multi/multi__spring_cloud_sleuth.html @@ -1,3 +1,3 @@ - Part VII. Spring Cloud Sleuth

Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

Prev   Next
44. Broadcasting Your Own Events Home 45. Introduction
\ No newline at end of file + Part VII. Spring Cloud Sleuth
Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Dalston.SR4

Prev   Next
44. Broadcasting Your Own Events Home 45. Introduction
\ No newline at end of file diff --git a/Dalston.SR4/multi/multi_pr01.html b/Dalston.SR4/multi/multi_pr01.html index c1944f54..c854191a 100644 --- a/Dalston.SR4/multi/multi_pr01.html +++ b/Dalston.SR4/multi/multi_pr01.html @@ -8,4 +8,4 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file +centres, and managed platforms such as Cloud Foundry.

Version: Dalston.SR4

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file diff --git a/Dalston.SR4/multi/multi_vault.config.backends.database-backends.html b/Dalston.SR4/multi/multi_vault.config.backends.database-backends.html index 0087cf54..de311aeb 100644 --- a/Dalston.SR4/multi/multi_vault.config.backends.database-backends.html +++ b/Dalston.SR4/multi/multi_vault.config.backends.database-backends.html @@ -10,7 +10,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> </dependencies>


[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Dalston.SR4/multi/multi_vault.config.backends.html b/Dalston.SR4/multi/multi_vault.config.backends.html index 01f66b59..eb5dff49 100644 --- a/Dalston.SR4/multi/multi_vault.config.backends.html +++ b/Dalston.SR4/multi/multi_vault.config.backends.html @@ -26,7 +26,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -43,7 +43,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -62,7 +62,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/Dalston.SR4/single/spring-cloud.html b/Dalston.SR4/single/spring-cloud.html index 426507f3..ce1e391f 100644 --- a/Dalston.SR4/single/spring-cloud.html +++ b/Dalston.SR4/single/spring-cloud.html @@ -8,7 +8,7 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases +centres, and managed platforms such as Cloud Foundry.

Version: Dalston.SR4

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases and extensibility mechanism to cover others.

  • Distributed/versioned configuration
  • Service registration and discovery
  • Routing
  • Service-to-service calls
  • Load balancing
  • Circuit Breakers
  • Distributed messaging

Part I. Cloud Native Applications

Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required.

Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul).

If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information:

Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using).

[Note]Note

Spring Cloud is released under the non-restrictive Apache 2.0 license. If you would like to contribute to this section of the documentation or if you find an error, please find the source code and issue trackers in the project at github.

2. Spring Cloud Context: Application Context Services

Spring Boot has an opinionated view of how to build an application with Spring: for instance it has conventional locations for common configuration file, and endpoints for common management and monitoring @@ -292,7 +292,7 @@ the @LoadBalanced qualifier when you create your

-

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
+

Part II. Spring Cloud Config

Dalston.SR4

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
 $ ../mvnw spring-boot:run

The server is a Spring Boot application so you can run it from your IDE instead if you prefer (the main class is ConfigServerApplication). Then try out a client:

$ curl localhost:8888/foo/development
@@ -1171,7 +1171,7 @@ in bootstrap.yml.
bootstrap.yml. 
       token: YourVaultToken

10.7 Vault

10.7.1 Nested Keys In Vault

Vault supports the ability to nest keys in a value stored in Vault. For example

echo -n '{"appA": {"secret": "appAsecret"}, "bar": "baz"}' | vault write secret/myapp -

This command will write a JSON object to your Vault. To access these values in Spring you would use the traditional dot(.) annotation. For example

@Value("${appA.secret}")
-String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration +String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

Dalston.SR4

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The @@ -3869,7 +3869,7 @@ package of BusConfiguration.

You can also exp }

All examples of @RemoteApplicationEventScan above are equivalent, in that the com.acme package will be registered by explicitly specifying the packages on @RemoteApplicationEventScan. Note, you can specify multiple base -packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

45. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

45.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an +packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Dalston.SR4

45. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

45.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an RPC. Span’s are identified by a unique 64-bit ID for the span and another 64-bit ID for the trace the span is a part of. Spans also have other data, such as descriptions, timestamped events, key-value annotations (tags), the ID of the span that caused them, and process ID’s (normally IP address).

Spans are started and stopped, and they keep track of their timing information. Once you create a @@ -4720,7 +4720,7 @@ subscribe events. To disable Spring Integration instrumentation, set

[Important]Important

When using the Executor to build a Spring Integration IntegrationFlow remember to use the untraced version of the Executor. Decorating Spring Integration Executor Channel with TraceableExecutorService will cause the spans to be improperly closed.

56.9 Zuul

We’re registering Zuul filters to propagate the tracing information (the request header is enriched with tracing data). -To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

57. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration +To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

57. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

Dalston.SR4

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The @@ -5195,7 +5195,7 @@ service called "sso", for instance, with credentials containing automatically to the Spring OAuth2 client that you enable with @EnableOAuth2Sso (from Spring Boot). The name of the service can be parameterized using spring.oauth2.sso.serviceId.

Part XII. Spring Cloud Contract

Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer

1.3.5.BUILD-SNAPSHOT

78. Spring Cloud Contract

What you always need is confidence in pushing new features into a new application or service in a distributed system. +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer

Dalston.SR4

78. Spring Cloud Contract

What you always need is confidence in pushing new features into a new application or service in a distributed system. This project provides support for Consumer Driven Contracts and service schemas in Spring applications, covering a range of options for writing tests, publishing them as assets, asserting that a contract is kept by producers and consumers, for HTTP and message-based interactions.

79. Spring Cloud Contract Verifier Introduction

[Tip]Tip

The Accurest project was initially started by Marcin Grzejszczak and Jakub Kubrynski (codearte.io)

Just to make long story short - Spring Cloud Contract Verifier is a tool that enables Consumer Driven Contract (CDC) development of JVM-based applications. It is shipped @@ -9316,7 +9316,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -9500,7 +9500,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -9517,7 +9517,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -9536,7 +9536,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) @@ -9560,7 +9560,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> </dependencies>


[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Dalston.SR4/spring-cloud.xml b/Dalston.SR4/spring-cloud.xml index ca9098d6..1e3c1952 100644 --- a/Dalston.SR4/spring-cloud.xml +++ b/Dalston.SR4/spring-cloud.xml @@ -17,7 +17,7 @@ Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data centres, and managed platforms such as Cloud Foundry. -Version: 1.3.5.BUILD-SNAPSHOT +Version: Dalston.SR4 Features @@ -538,7 +538,7 @@ public class MyClass { Spring Cloud Config -1.3.5.BUILD-SNAPSHOT +Dalston.SR4 Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration. @@ -1987,7 +1987,7 @@ String name = "World"; Spring Cloud Netflix -1.3.5.BUILD-SNAPSHOT +Dalston.SR4 This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -8102,7 +8102,7 @@ packages to scan. Spring Cloud Sleuth Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer -1.3.5.BUILD-SNAPSHOT +Dalston.SR4 Introduction @@ -9886,7 +9886,7 @@ To disable Zuul support set the spring.sleuth.zuul.enabled pr Spring Cloud Consul -1.3.5.BUILD-SNAPSHOT +Dalston.SR4 This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -10939,7 +10939,7 @@ parameterized using spring.oauth2.sso.serviceId. Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer -1.3.5.BUILD-SNAPSHOT +Dalston.SR4 Spring Cloud Contract @@ -17264,7 +17264,7 @@ the test cases). Example Maven configuration: <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -17748,7 +17748,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> </dependencies> @@ -17794,7 +17794,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> </dependencies> @@ -17845,7 +17845,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> </dependencies> @@ -17917,7 +17917,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR4</version> </dependency> </dependencies> diff --git a/Dalston.SR5/index.html b/Dalston.SR5/index.html index 6b5b9e65..95d23f3d 100644 --- a/Dalston.SR5/index.html +++ b/Dalston.SR5/index.html @@ -90,7 +90,7 @@ $(addBlockSwitches);

-

1.3.5.BUILD-SNAPSHOT

+

Dalston.SR5

diff --git a/Dalston.SR5/multi/multi__client_side_usage_2.html b/Dalston.SR5/multi/multi__client_side_usage_2.html index df67d2fe..9d43e11a 100644 --- a/Dalston.SR5/multi/multi__client_side_usage_2.html +++ b/Dalston.SR5/multi/multi__client_side_usage_2.html @@ -13,7 +13,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> diff --git a/Dalston.SR5/multi/multi__spring_cloud_config.html b/Dalston.SR5/multi/multi__spring_cloud_config.html index de19730e..1583a1bf 100644 --- a/Dalston.SR5/multi/multi__spring_cloud_config.html +++ b/Dalston.SR5/multi/multi__spring_cloud_config.html @@ -1,3 +1,3 @@ - Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file + Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

Dalston.SR5

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file diff --git a/Dalston.SR5/multi/multi__spring_cloud_consul.html b/Dalston.SR5/multi/multi__spring_cloud_consul.html index d69d2ee2..6cbbedec 100644 --- a/Dalston.SR5/multi/multi__spring_cloud_consul.html +++ b/Dalston.SR5/multi/multi__spring_cloud_consul.html @@ -1,6 +1,6 @@ - Part VIII. Spring Cloud Consul
Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration + Part VIII. Spring Cloud Consul

Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

Dalston.SR5

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The diff --git a/Dalston.SR5/multi/multi__spring_cloud_contract.html b/Dalston.SR5/multi/multi__spring_cloud_contract.html index a10ed152..bf14d130 100644 --- a/Dalston.SR5/multi/multi__spring_cloud_contract.html +++ b/Dalston.SR5/multi/multi__spring_cloud_contract.html @@ -1,4 +1,4 @@ Part XII. Spring Cloud Contract

Part XII. Spring Cloud Contract
Prev   Next

Part XII. Spring Cloud Contract

Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer

1.3.5.BUILD-SNAPSHOT

Prev   Next
77. Single Sign On Home 78. Spring Cloud Contract
\ No newline at end of file +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer

Dalston.SR5

Prev   Next
77. Single Sign On Home 78. Spring Cloud Contract
\ No newline at end of file diff --git a/Dalston.SR5/multi/multi__spring_cloud_netflix.html b/Dalston.SR5/multi/multi__spring_cloud_netflix.html index 874cb141..ead40e0a 100644 --- a/Dalston.SR5/multi/multi__spring_cloud_netflix.html +++ b/Dalston.SR5/multi/multi__spring_cloud_netflix.html @@ -1,6 +1,6 @@ - Part III. Spring Cloud Netflix
Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration + Part III. Spring Cloud Netflix

Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

Dalston.SR5

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The diff --git a/Dalston.SR5/multi/multi__spring_cloud_sleuth.html b/Dalston.SR5/multi/multi__spring_cloud_sleuth.html index cd824b23..dd3e8e8e 100644 --- a/Dalston.SR5/multi/multi__spring_cloud_sleuth.html +++ b/Dalston.SR5/multi/multi__spring_cloud_sleuth.html @@ -1,3 +1,3 @@ - Part VII. Spring Cloud Sleuth

Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

Prev   Next
44. Broadcasting Your Own Events Home 45. Introduction
\ No newline at end of file + Part VII. Spring Cloud Sleuth
Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Dalston.SR5

Prev   Next
44. Broadcasting Your Own Events Home 45. Introduction
\ No newline at end of file diff --git a/Dalston.SR5/multi/multi_pr01.html b/Dalston.SR5/multi/multi_pr01.html index c1944f54..b7eed87e 100644 --- a/Dalston.SR5/multi/multi_pr01.html +++ b/Dalston.SR5/multi/multi_pr01.html @@ -8,4 +8,4 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file +centres, and managed platforms such as Cloud Foundry.

Version: Dalston.SR5

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file diff --git a/Dalston.SR5/multi/multi_vault.config.backends.database-backends.html b/Dalston.SR5/multi/multi_vault.config.backends.database-backends.html index 7b9ec2f1..3b42229f 100644 --- a/Dalston.SR5/multi/multi_vault.config.backends.database-backends.html +++ b/Dalston.SR5/multi/multi_vault.config.backends.database-backends.html @@ -10,7 +10,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> </dependencies>


[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Dalston.SR5/multi/multi_vault.config.backends.html b/Dalston.SR5/multi/multi_vault.config.backends.html index a41b9ddc..8c9d9cf6 100644 --- a/Dalston.SR5/multi/multi_vault.config.backends.html +++ b/Dalston.SR5/multi/multi_vault.config.backends.html @@ -26,7 +26,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -43,7 +43,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -62,7 +62,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/Dalston.SR5/single/spring-cloud.html b/Dalston.SR5/single/spring-cloud.html index 6e571a10..1342f45b 100644 --- a/Dalston.SR5/single/spring-cloud.html +++ b/Dalston.SR5/single/spring-cloud.html @@ -8,7 +8,7 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases +centres, and managed platforms such as Cloud Foundry.

Version: Dalston.SR5

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases and extensibility mechanism to cover others.

  • Distributed/versioned configuration
  • Service registration and discovery
  • Routing
  • Service-to-service calls
  • Load balancing
  • Circuit Breakers
  • Distributed messaging

Part I. Cloud Native Applications

Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required.

Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul).

If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information:

Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using).

[Note]Note

Spring Cloud is released under the non-restrictive Apache 2.0 license. If you would like to contribute to this section of the documentation or if you find an error, please find the source code and issue trackers in the project at github.

2. Spring Cloud Context: Application Context Services

Spring Boot has an opinionated view of how to build an application with Spring: for instance it has conventional locations for common configuration file, and endpoints for common management and monitoring @@ -292,7 +292,7 @@ the @LoadBalanced qualifier when you create your

-

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
+

Part II. Spring Cloud Config

Dalston.SR5

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
 $ ../mvnw spring-boot:run

The server is a Spring Boot application so you can run it from your IDE instead if you prefer (the main class is ConfigServerApplication). Then try out a client:

$ curl localhost:8888/foo/development
@@ -1171,7 +1171,7 @@ in bootstrap.yml.
bootstrap.yml. 
       token: YourVaultToken

10.7 Vault

10.7.1 Nested Keys In Vault

Vault supports the ability to nest keys in a value stored in Vault. For example

echo -n '{"appA": {"secret": "appAsecret"}, "bar": "baz"}' | vault write secret/myapp -

This command will write a JSON object to your Vault. To access these values in Spring you would use the traditional dot(.) annotation. For example

@Value("${appA.secret}")
-String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration +String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

Dalston.SR5

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The @@ -3869,7 +3869,7 @@ package of BusConfiguration.

You can also exp }

All examples of @RemoteApplicationEventScan above are equivalent, in that the com.acme package will be registered by explicitly specifying the packages on @RemoteApplicationEventScan. Note, you can specify multiple base -packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

45. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

45.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an +packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Dalston.SR5

45. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

45.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an RPC. Span’s are identified by a unique 64-bit ID for the span and another 64-bit ID for the trace the span is a part of. Spans also have other data, such as descriptions, timestamped events, key-value annotations (tags), the ID of the span that caused them, and process ID’s (normally IP address).

Spans are started and stopped, and they keep track of their timing information. Once you create a @@ -4723,7 +4723,7 @@ subscribe events. To disable Spring Integration instrumentation, set

[Important]Important

When using the Executor to build a Spring Integration IntegrationFlow remember to use the untraced version of the Executor. Decorating Spring Integration Executor Channel with TraceableExecutorService will cause the spans to be improperly closed.

56.9 Zuul

We’re registering Zuul filters to propagate the tracing information (the request header is enriched with tracing data). -To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

57. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration +To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

57. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

Dalston.SR5

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The @@ -5198,7 +5198,7 @@ service called "sso", for instance, with credentials containing automatically to the Spring OAuth2 client that you enable with @EnableOAuth2Sso (from Spring Boot). The name of the service can be parameterized using spring.oauth2.sso.serviceId.

Part XII. Spring Cloud Contract

Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer

1.3.5.BUILD-SNAPSHOT

78. Spring Cloud Contract

What you always need is confidence in pushing new features into a new application or service in a distributed system. +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer

Dalston.SR5

78. Spring Cloud Contract

What you always need is confidence in pushing new features into a new application or service in a distributed system. This project provides support for Consumer Driven Contracts and service schemas in Spring applications, covering a range of options for writing tests, publishing them as assets, asserting that a contract is kept by producers and consumers, for HTTP and message-based interactions.

79. Spring Cloud Contract Verifier Introduction

[Tip]Tip

The Accurest project was initially started by Marcin Grzejszczak and Jakub Kubrynski (codearte.io)

Just to make long story short - Spring Cloud Contract Verifier is a tool that enables Consumer Driven Contract (CDC) development of JVM-based applications. It is shipped @@ -9384,7 +9384,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -9568,7 +9568,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -9585,7 +9585,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -9604,7 +9604,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) @@ -9628,7 +9628,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> </dependencies>


[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Dalston.SR5/spring-cloud.xml b/Dalston.SR5/spring-cloud.xml index cfde4370..829cb792 100644 --- a/Dalston.SR5/spring-cloud.xml +++ b/Dalston.SR5/spring-cloud.xml @@ -17,7 +17,7 @@ Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data centres, and managed platforms such as Cloud Foundry. -Version: 1.3.5.BUILD-SNAPSHOT +Version: Dalston.SR5 Features @@ -538,7 +538,7 @@ public class MyClass { Spring Cloud Config -1.3.5.BUILD-SNAPSHOT +Dalston.SR5 Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration. @@ -1987,7 +1987,7 @@ String name = "World"; Spring Cloud Netflix -1.3.5.BUILD-SNAPSHOT +Dalston.SR5 This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -8102,7 +8102,7 @@ packages to scan. Spring Cloud Sleuth Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer -1.3.5.BUILD-SNAPSHOT +Dalston.SR5 Introduction @@ -9892,7 +9892,7 @@ To disable Zuul support set the spring.sleuth.zuul.enabled pr Spring Cloud Consul -1.3.5.BUILD-SNAPSHOT +Dalston.SR5 This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -10945,7 +10945,7 @@ parameterized using spring.oauth2.sso.serviceId. Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer -1.3.5.BUILD-SNAPSHOT +Dalston.SR5 Spring Cloud Contract @@ -17409,7 +17409,7 @@ the test cases). Example Maven configuration: <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -17893,7 +17893,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> </dependencies> @@ -17939,7 +17939,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> </dependencies> @@ -17990,7 +17990,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> </dependencies> @@ -18062,7 +18062,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Dalston.SR5</version> </dependency> </dependencies> diff --git a/Edgware.RC1/index.html b/Edgware.RC1/index.html index 6b5b9e65..23fb406b 100644 --- a/Edgware.RC1/index.html +++ b/Edgware.RC1/index.html @@ -90,7 +90,7 @@ $(addBlockSwitches);

-

1.3.5.BUILD-SNAPSHOT

+

Edgware.RC1

diff --git a/Edgware.RC1/multi/multi__client_side_usage_2.html b/Edgware.RC1/multi/multi__client_side_usage_2.html index 4e70dfe1..3eccdc39 100644 --- a/Edgware.RC1/multi/multi__client_side_usage_2.html +++ b/Edgware.RC1/multi/multi__client_side_usage_2.html @@ -13,7 +13,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> diff --git a/Edgware.RC1/multi/multi__spring_cloud_config.html b/Edgware.RC1/multi/multi__spring_cloud_config.html index de19730e..83920fd1 100644 --- a/Edgware.RC1/multi/multi__spring_cloud_config.html +++ b/Edgware.RC1/multi/multi__spring_cloud_config.html @@ -1,3 +1,3 @@ - Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file + Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

Edgware.RC1

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file diff --git a/Edgware.RC1/multi/multi__spring_cloud_consul.html b/Edgware.RC1/multi/multi__spring_cloud_consul.html index d2837e7d..67977846 100644 --- a/Edgware.RC1/multi/multi__spring_cloud_consul.html +++ b/Edgware.RC1/multi/multi__spring_cloud_consul.html @@ -1,6 +1,6 @@ - Part VIII. Spring Cloud Consul
Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration + Part VIII. Spring Cloud Consul

Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

Edgware.RC1

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The diff --git a/Edgware.RC1/multi/multi__spring_cloud_contract.html b/Edgware.RC1/multi/multi__spring_cloud_contract.html index 7355da54..950b63da 100644 --- a/Edgware.RC1/multi/multi__spring_cloud_contract.html +++ b/Edgware.RC1/multi/multi__spring_cloud_contract.html @@ -1,4 +1,4 @@ Part XII. Spring Cloud Contract

Part XII. Spring Cloud Contract
Prev   Next

Part XII. Spring Cloud Contract

Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

1.3.5.BUILD-SNAPSHOT

Prev   Next
79. Single Sign On Home 80. Spring Cloud Contract
\ No newline at end of file +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

Edgware.RC1

Prev   Next
79. Single Sign On Home 80. Spring Cloud Contract
\ No newline at end of file diff --git a/Edgware.RC1/multi/multi__spring_cloud_netflix.html b/Edgware.RC1/multi/multi__spring_cloud_netflix.html index 874cb141..7a5c7f6b 100644 --- a/Edgware.RC1/multi/multi__spring_cloud_netflix.html +++ b/Edgware.RC1/multi/multi__spring_cloud_netflix.html @@ -1,6 +1,6 @@ - Part III. Spring Cloud Netflix
Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration + Part III. Spring Cloud Netflix

Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

Edgware.RC1

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The diff --git a/Edgware.RC1/multi/multi__spring_cloud_sleuth.html b/Edgware.RC1/multi/multi__spring_cloud_sleuth.html index b42d45e1..4adf14b5 100644 --- a/Edgware.RC1/multi/multi__spring_cloud_sleuth.html +++ b/Edgware.RC1/multi/multi__spring_cloud_sleuth.html @@ -1,3 +1,3 @@ - Part VII. Spring Cloud Sleuth

Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

Prev   Next
45. Broadcasting Your Own Events Home 46. Introduction
\ No newline at end of file + Part VII. Spring Cloud Sleuth
Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Edgware.RC1

Prev   Next
45. Broadcasting Your Own Events Home 46. Introduction
\ No newline at end of file diff --git a/Edgware.RC1/multi/multi_pr01.html b/Edgware.RC1/multi/multi_pr01.html index c1944f54..7d31d1c9 100644 --- a/Edgware.RC1/multi/multi_pr01.html +++ b/Edgware.RC1/multi/multi_pr01.html @@ -8,4 +8,4 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file +centres, and managed platforms such as Cloud Foundry.

Version: Edgware.RC1

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file diff --git a/Edgware.RC1/multi/multi_vault.config.backends.database-backends.html b/Edgware.RC1/multi/multi_vault.config.backends.database-backends.html index 0bf2f763..4e4897e7 100644 --- a/Edgware.RC1/multi/multi_vault.config.backends.database-backends.html +++ b/Edgware.RC1/multi/multi_vault.config.backends.database-backends.html @@ -13,7 +13,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Edgware.RC1/multi/multi_vault.config.backends.html b/Edgware.RC1/multi/multi_vault.config.backends.html index 4dc3fff4..43be0ff2 100644 --- a/Edgware.RC1/multi/multi_vault.config.backends.html +++ b/Edgware.RC1/multi/multi_vault.config.backends.html @@ -26,7 +26,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -43,7 +43,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -62,7 +62,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/Edgware.RC1/single/spring-cloud.html b/Edgware.RC1/single/spring-cloud.html index 5ef06895..5bb4d8e6 100644 --- a/Edgware.RC1/single/spring-cloud.html +++ b/Edgware.RC1/single/spring-cloud.html @@ -8,7 +8,7 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases +centres, and managed platforms such as Cloud Foundry.

Version: Edgware.RC1

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases and extensibility mechanism to cover others.

  • Distributed/versioned configuration
  • Service registration and discovery
  • Routing
  • Service-to-service calls
  • Load balancing
  • Circuit Breakers
  • Distributed messaging

Part I. Cloud Native Applications

Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required.

Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul).

If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information:

Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using).

[Note]Note

Spring Cloud is released under the non-restrictive Apache 2.0 license. If you would like to contribute to this section of the documentation or if you find an error, please find the source code and issue trackers in the project at github.

2. Spring Cloud Context: Application Context Services

Spring Boot has an opinionated view of how to build an application with Spring: for instance it has conventional locations for common configuration file, and endpoints for common management and monitoring @@ -301,7 +301,7 @@ HTTP client and OkHttpClientConnectionPoolFactory f your own implementation of these beans if you would like to customize how the HTTP clients are created in downstream projects. You can also disable the creation of these beans by setting spring.cloud.httpclientfactories.apache.enabled or spring.cloud.httpclientfactories.ok.enabled to -false.

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
+false.

Part II. Spring Cloud Config

Edgware.RC1

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
 $ ../mvnw spring-boot:run

The server is a Spring Boot application so you can run it from your IDE instead if you prefer (the main class is ConfigServerApplication). Then try out a client:

$ curl localhost:8888/foo/development
@@ -1194,7 +1194,7 @@ in bootstrap.yml.
bootstrap.yml. 
       token: YourVaultToken

10.7 Vault

10.7.1 Nested Keys In Vault

Vault supports the ability to nest keys in a value stored in Vault. For example

echo -n '{"appA": {"secret": "appAsecret"}, "bar": "baz"}' | vault write secret/myapp -

This command will write a JSON object to your Vault. To access these values in Spring you would use the traditional dot(.) annotation. For example

@Value("${appA.secret}")
-String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration +String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

Edgware.RC1

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The @@ -4240,7 +4240,7 @@ package of BusConfiguration.

You can also exp }

All examples of @RemoteApplicationEventScan above are equivalent, in that the com.acme package will be registered by explicitly specifying the packages on @RemoteApplicationEventScan. Note, you can specify multiple base -packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

46. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

46.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an +packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Edgware.RC1

46. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

46.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an RPC. Span’s are identified by a unique 64-bit ID for the span and another 64-bit ID for the trace the span is a part of. Spans also have other data, such as descriptions, timestamped events, key-value annotations (tags), the ID of the span that caused them, and process ID’s (normally IP address).

Spans are started and stopped, and they keep track of their timing information. Once you create a @@ -5035,7 +5035,7 @@ subscribe events. To disable Spring Integration instrumentation, set

[Important]Important

When using the Executor to build a Spring Integration IntegrationFlow remember to use the untraced version of the Executor. Decorating Spring Integration Executor Channel with TraceableExecutorService will cause the spans to be improperly closed.

58.9 Zuul

We’re registering Zuul filters to propagate the tracing information (the request header is enriched with tracing data). -To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

59. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration +To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

59. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

Edgware.RC1

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The @@ -5519,7 +5519,7 @@ service called "sso", for instance, with credentials containing automatically to the Spring OAuth2 client that you enable with @EnableOAuth2Sso (from Spring Boot). The name of the service can be parameterized using spring.oauth2.sso.serviceId.

Part XII. Spring Cloud Contract

Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

1.3.5.BUILD-SNAPSHOT

80. Spring Cloud Contract

You need confidence when pushing new features to a new application or service in a +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

Edgware.RC1

80. Spring Cloud Contract

You need confidence when pushing new features to a new application or service in a distributed system. This project provides support for Consumer Driven Contracts and service schemas in Spring applications (for both HTTP and message-based interactions), covering a range of options for writing tests, publishing them as assets, and asserting @@ -10132,7 +10132,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -10319,7 +10319,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -10336,7 +10336,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -10355,7 +10355,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) @@ -10382,7 +10382,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Edgware.RC1/spring-cloud.xml b/Edgware.RC1/spring-cloud.xml index fd81c5fe..f19ccf85 100644 --- a/Edgware.RC1/spring-cloud.xml +++ b/Edgware.RC1/spring-cloud.xml @@ -17,7 +17,7 @@ Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data centres, and managed platforms such as Cloud Foundry. -Version: 1.3.5.BUILD-SNAPSHOT +Version: Edgware.RC1 Features @@ -558,7 +558,7 @@ in downstream projects. You can also disable the creation of these beans by set Spring Cloud Config -1.3.5.BUILD-SNAPSHOT +Edgware.RC1 Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration. @@ -2037,7 +2037,7 @@ String name = "World"; Spring Cloud Netflix -1.3.5.BUILD-SNAPSHOT +Edgware.RC1 This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -8813,7 +8813,7 @@ packages to scan. Spring Cloud Sleuth Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer -1.3.5.BUILD-SNAPSHOT +Edgware.RC1 Introduction @@ -10516,7 +10516,7 @@ To disable Zuul support set the spring.sleuth.zuul.enabled pr Spring Cloud Consul -1.3.5.BUILD-SNAPSHOT +Edgware.RC1 This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -11591,7 +11591,7 @@ parameterized using spring.oauth2.sso.serviceId. Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant -1.3.5.BUILD-SNAPSHOT +Edgware.RC1 Spring Cloud Contract @@ -18744,7 +18744,7 @@ the test cases). Example Maven configuration: <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -19237,7 +19237,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> </dependencies> @@ -19283,7 +19283,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> </dependencies> @@ -19334,7 +19334,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RC1</version> </dependency> </dependencies> @@ -19410,7 +19410,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=database diff --git a/Edgware.RELEASE/multi/multi__client_side_usage_2.html b/Edgware.RELEASE/multi/multi__client_side_usage_2.html index ae189140..909a1288 100644 --- a/Edgware.RELEASE/multi/multi__client_side_usage_2.html +++ b/Edgware.RELEASE/multi/multi__client_side_usage_2.html @@ -13,7 +13,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> diff --git a/Edgware.RELEASE/multi/multi__spring_cloud_config.html b/Edgware.RELEASE/multi/multi__spring_cloud_config.html index de19730e..7d9687ea 100644 --- a/Edgware.RELEASE/multi/multi__spring_cloud_config.html +++ b/Edgware.RELEASE/multi/multi__spring_cloud_config.html @@ -1,3 +1,3 @@ - Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file + Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

Edgware.RELEASE

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file diff --git a/Edgware.RELEASE/multi/multi__spring_cloud_consul.html b/Edgware.RELEASE/multi/multi__spring_cloud_consul.html index d2837e7d..25f87a39 100644 --- a/Edgware.RELEASE/multi/multi__spring_cloud_consul.html +++ b/Edgware.RELEASE/multi/multi__spring_cloud_consul.html @@ -1,6 +1,6 @@ - Part VIII. Spring Cloud Consul
Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration + Part VIII. Spring Cloud Consul

Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

Edgware.RELEASE

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The diff --git a/Edgware.RELEASE/multi/multi__spring_cloud_contract.html b/Edgware.RELEASE/multi/multi__spring_cloud_contract.html index 7355da54..3bb4e3cf 100644 --- a/Edgware.RELEASE/multi/multi__spring_cloud_contract.html +++ b/Edgware.RELEASE/multi/multi__spring_cloud_contract.html @@ -1,4 +1,4 @@ Part XII. Spring Cloud Contract

Part XII. Spring Cloud Contract
Prev   Next

Part XII. Spring Cloud Contract

Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

1.3.5.BUILD-SNAPSHOT

Prev   Next
79. Single Sign On Home 80. Spring Cloud Contract
\ No newline at end of file +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

Edgware.RELEASE

Prev   Next
79. Single Sign On Home 80. Spring Cloud Contract
\ No newline at end of file diff --git a/Edgware.RELEASE/multi/multi__spring_cloud_netflix.html b/Edgware.RELEASE/multi/multi__spring_cloud_netflix.html index 874cb141..3aa52544 100644 --- a/Edgware.RELEASE/multi/multi__spring_cloud_netflix.html +++ b/Edgware.RELEASE/multi/multi__spring_cloud_netflix.html @@ -1,6 +1,6 @@ - Part III. Spring Cloud Netflix
Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration + Part III. Spring Cloud Netflix

Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

Edgware.RELEASE

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The diff --git a/Edgware.RELEASE/multi/multi__spring_cloud_sleuth.html b/Edgware.RELEASE/multi/multi__spring_cloud_sleuth.html index b42d45e1..dcfc498d 100644 --- a/Edgware.RELEASE/multi/multi__spring_cloud_sleuth.html +++ b/Edgware.RELEASE/multi/multi__spring_cloud_sleuth.html @@ -1,3 +1,3 @@ - Part VII. Spring Cloud Sleuth

Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

Prev   Next
45. Broadcasting Your Own Events Home 46. Introduction
\ No newline at end of file + Part VII. Spring Cloud Sleuth
Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Edgware.RELEASE

Prev   Next
45. Broadcasting Your Own Events Home 46. Introduction
\ No newline at end of file diff --git a/Edgware.RELEASE/multi/multi_pr01.html b/Edgware.RELEASE/multi/multi_pr01.html index c1944f54..e51a4ee9 100644 --- a/Edgware.RELEASE/multi/multi_pr01.html +++ b/Edgware.RELEASE/multi/multi_pr01.html @@ -8,4 +8,4 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file +centres, and managed platforms such as Cloud Foundry.

Version: Edgware.RELEASE

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file diff --git a/Edgware.RELEASE/multi/multi_vault.config.backends.database-backends.html b/Edgware.RELEASE/multi/multi_vault.config.backends.database-backends.html index 2e4b27da..24d72af8 100644 --- a/Edgware.RELEASE/multi/multi_vault.config.backends.database-backends.html +++ b/Edgware.RELEASE/multi/multi_vault.config.backends.database-backends.html @@ -13,7 +13,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Edgware.RELEASE/multi/multi_vault.config.backends.html b/Edgware.RELEASE/multi/multi_vault.config.backends.html index 4c29c87b..34a8a283 100644 --- a/Edgware.RELEASE/multi/multi_vault.config.backends.html +++ b/Edgware.RELEASE/multi/multi_vault.config.backends.html @@ -26,7 +26,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -43,7 +43,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -62,7 +62,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/Edgware.RELEASE/single/spring-cloud.html b/Edgware.RELEASE/single/spring-cloud.html index 135adbc8..3044ebfc 100644 --- a/Edgware.RELEASE/single/spring-cloud.html +++ b/Edgware.RELEASE/single/spring-cloud.html @@ -8,7 +8,7 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases +centres, and managed platforms such as Cloud Foundry.

Version: Edgware.RELEASE

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases and extensibility mechanism to cover others.

  • Distributed/versioned configuration
  • Service registration and discovery
  • Routing
  • Service-to-service calls
  • Load balancing
  • Circuit Breakers
  • Distributed messaging

Part I. Cloud Native Applications

Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required.

Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul).

If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information:

Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using).

[Note]Note

Spring Cloud is released under the non-restrictive Apache 2.0 license. If you would like to contribute to this section of the documentation or if you find an error, please find the source code and issue trackers in the project at github.

2. Spring Cloud Context: Application Context Services

Spring Boot has an opinionated view of how to build an application with Spring: for instance it has conventional locations for common configuration file, and endpoints for common management and monitoring @@ -314,7 +314,7 @@ HTTP client and OkHttpClientConnectionPoolFactory f your own implementation of these beans if you would like to customize how the HTTP clients are created in downstream projects. You can also disable the creation of these beans by setting spring.cloud.httpclientfactories.apache.enabled or spring.cloud.httpclientfactories.ok.enabled to -false.

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
+false.

Part II. Spring Cloud Config

Edgware.RELEASE

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
 $ ../mvnw spring-boot:run

The server is a Spring Boot application so you can run it from your IDE instead if you prefer (the main class is ConfigServerApplication). Then try out a client:

$ curl localhost:8888/foo/development
@@ -1216,7 +1216,7 @@ in bootstrap.yml.
bootstrap.yml. 
       token: YourVaultToken

10.7 Vault

10.7.1 Nested Keys In Vault

Vault supports the ability to nest keys in a value stored in Vault. For example

echo -n '{"appA": {"secret": "appAsecret"}, "bar": "baz"}' | vault write secret/myapp -

This command will write a JSON object to your Vault. To access these values in Spring you would use the traditional dot(.) annotation. For example

@Value("${appA.secret}")
-String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration +String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

Edgware.RELEASE

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The @@ -4291,7 +4291,7 @@ package of BusConfiguration.

You can also exp }

All examples of @RemoteApplicationEventScan above are equivalent, in that the com.acme package will be registered by explicitly specifying the packages on @RemoteApplicationEventScan. Note, you can specify multiple base -packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

46. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

46.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an +packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Edgware.RELEASE

46. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

46.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an RPC. Span’s are identified by a unique 64-bit ID for the span and another 64-bit ID for the trace the span is a part of. Spans also have other data, such as descriptions, timestamped events, key-value annotations (tags), the ID of the span that caused them, and process ID’s (normally IP address).

Spans are started and stopped, and they keep track of their timing information. Once you create a @@ -5086,7 +5086,7 @@ subscribe events. To disable Spring Integration instrumentation, set

[Important]Important

When using the Executor to build a Spring Integration IntegrationFlow remember to use the untraced version of the Executor. Decorating Spring Integration Executor Channel with TraceableExecutorService will cause the spans to be improperly closed.

58.9 Zuul

We’re registering Zuul filters to propagate the tracing information (the request header is enriched with tracing data). -To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

59. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration +To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

59. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

Edgware.RELEASE

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The @@ -5570,7 +5570,7 @@ service called "sso", for instance, with credentials containing automatically to the Spring OAuth2 client that you enable with @EnableOAuth2Sso (from Spring Boot). The name of the service can be parameterized using spring.oauth2.sso.serviceId.

Part XII. Spring Cloud Contract

Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

1.3.5.BUILD-SNAPSHOT

80. Spring Cloud Contract

You need confidence when pushing new features to a new application or service in a +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

Edgware.RELEASE

80. Spring Cloud Contract

You need confidence when pushing new features to a new application or service in a distributed system. This project provides support for Consumer Driven Contracts and service schemas in Spring applications (for both HTTP and message-based interactions), covering a range of options for writing tests, publishing them as assets, and asserting @@ -10468,7 +10468,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -10681,7 +10681,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -10698,7 +10698,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -10717,7 +10717,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) @@ -10744,7 +10744,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Edgware.RELEASE/spring-cloud.xml b/Edgware.RELEASE/spring-cloud.xml index bbce84e1..0dec0387 100644 --- a/Edgware.RELEASE/spring-cloud.xml +++ b/Edgware.RELEASE/spring-cloud.xml @@ -17,7 +17,7 @@ Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data centres, and managed platforms such as Cloud Foundry. -Version: 1.3.5.BUILD-SNAPSHOT +Version: Edgware.RELEASE Features @@ -573,7 +573,7 @@ in downstream projects. You can also disable the creation of these beans by set Spring Cloud Config -1.3.5.BUILD-SNAPSHOT +Edgware.RELEASE Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration. @@ -2064,7 +2064,7 @@ String name = "World"; Spring Cloud Netflix -1.3.5.BUILD-SNAPSHOT +Edgware.RELEASE This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -8891,7 +8891,7 @@ packages to scan. Spring Cloud Sleuth Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer -1.3.5.BUILD-SNAPSHOT +Edgware.RELEASE Introduction @@ -10594,7 +10594,7 @@ To disable Zuul support set the spring.sleuth.zuul.enabled pr Spring Cloud Consul -1.3.5.BUILD-SNAPSHOT +Edgware.RELEASE This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -11669,7 +11669,7 @@ parameterized using spring.oauth2.sso.serviceId. Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant -1.3.5.BUILD-SNAPSHOT +Edgware.RELEASE Spring Cloud Contract @@ -19266,7 +19266,7 @@ the test cases). Example Maven configuration: <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -19838,7 +19838,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> </dependencies> @@ -19884,7 +19884,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> </dependencies> @@ -19935,7 +19935,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.RELEASE</version> </dependency> </dependencies> @@ -20011,7 +20011,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=database diff --git a/Edgware.SR1/multi/multi__client_side_usage_2.html b/Edgware.SR1/multi/multi__client_side_usage_2.html index 541a04d6..3c2e56f9 100644 --- a/Edgware.SR1/multi/multi__client_side_usage_2.html +++ b/Edgware.SR1/multi/multi__client_side_usage_2.html @@ -13,7 +13,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> diff --git a/Edgware.SR1/multi/multi__spring_cloud_config.html b/Edgware.SR1/multi/multi__spring_cloud_config.html index de19730e..5488ad35 100644 --- a/Edgware.SR1/multi/multi__spring_cloud_config.html +++ b/Edgware.SR1/multi/multi__spring_cloud_config.html @@ -1,3 +1,3 @@ - Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file + Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

Edgware.SR1

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file diff --git a/Edgware.SR1/multi/multi__spring_cloud_consul.html b/Edgware.SR1/multi/multi__spring_cloud_consul.html index d2837e7d..e18f2888 100644 --- a/Edgware.SR1/multi/multi__spring_cloud_consul.html +++ b/Edgware.SR1/multi/multi__spring_cloud_consul.html @@ -1,6 +1,6 @@ - Part VIII. Spring Cloud Consul
Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration + Part VIII. Spring Cloud Consul

Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

Edgware.SR1

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The diff --git a/Edgware.SR1/multi/multi__spring_cloud_contract.html b/Edgware.SR1/multi/multi__spring_cloud_contract.html index a1b4863c..7e6ddacd 100644 --- a/Edgware.SR1/multi/multi__spring_cloud_contract.html +++ b/Edgware.SR1/multi/multi__spring_cloud_contract.html @@ -1,4 +1,4 @@ Part XII. Spring Cloud Contract

Part XII. Spring Cloud Contract
Prev   Next

Part XII. Spring Cloud Contract

_Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

1.3.5.BUILD-SNAPSHOT

Prev   Next
79. Single Sign On Home 80. Spring Cloud Contract
\ No newline at end of file +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

Edgware.SR1

Prev   Next
79. Single Sign On Home 80. Spring Cloud Contract
\ No newline at end of file diff --git a/Edgware.SR1/multi/multi__spring_cloud_netflix.html b/Edgware.SR1/multi/multi__spring_cloud_netflix.html index 874cb141..1d96a200 100644 --- a/Edgware.SR1/multi/multi__spring_cloud_netflix.html +++ b/Edgware.SR1/multi/multi__spring_cloud_netflix.html @@ -1,6 +1,6 @@ - Part III. Spring Cloud Netflix
Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration + Part III. Spring Cloud Netflix

Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

Edgware.SR1

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The diff --git a/Edgware.SR1/multi/multi__spring_cloud_sleuth.html b/Edgware.SR1/multi/multi__spring_cloud_sleuth.html index b42d45e1..c5046814 100644 --- a/Edgware.SR1/multi/multi__spring_cloud_sleuth.html +++ b/Edgware.SR1/multi/multi__spring_cloud_sleuth.html @@ -1,3 +1,3 @@ - Part VII. Spring Cloud Sleuth

Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

Prev   Next
45. Broadcasting Your Own Events Home 46. Introduction
\ No newline at end of file + Part VII. Spring Cloud Sleuth
Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Edgware.SR1

Prev   Next
45. Broadcasting Your Own Events Home 46. Introduction
\ No newline at end of file diff --git a/Edgware.SR1/multi/multi_pr01.html b/Edgware.SR1/multi/multi_pr01.html index c1944f54..512d1a12 100644 --- a/Edgware.SR1/multi/multi_pr01.html +++ b/Edgware.SR1/multi/multi_pr01.html @@ -8,4 +8,4 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file +centres, and managed platforms such as Cloud Foundry.

Version: Edgware.SR1

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file diff --git a/Edgware.SR1/multi/multi_vault.config.backends.database-backends.html b/Edgware.SR1/multi/multi_vault.config.backends.database-backends.html index 24dc4fd9..627af5d7 100644 --- a/Edgware.SR1/multi/multi_vault.config.backends.database-backends.html +++ b/Edgware.SR1/multi/multi_vault.config.backends.database-backends.html @@ -13,7 +13,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Edgware.SR1/multi/multi_vault.config.backends.html b/Edgware.SR1/multi/multi_vault.config.backends.html index adb8807c..4ae4732a 100644 --- a/Edgware.SR1/multi/multi_vault.config.backends.html +++ b/Edgware.SR1/multi/multi_vault.config.backends.html @@ -26,7 +26,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -43,7 +43,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -62,7 +62,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/Edgware.SR1/single/spring-cloud.html b/Edgware.SR1/single/spring-cloud.html index 3f7d95ca..0c3c9f67 100644 --- a/Edgware.SR1/single/spring-cloud.html +++ b/Edgware.SR1/single/spring-cloud.html @@ -8,7 +8,7 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases +centres, and managed platforms such as Cloud Foundry.

Version: Edgware.SR1

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases and extensibility mechanism to cover others.

  • Distributed/versioned configuration
  • Service registration and discovery
  • Routing
  • Service-to-service calls
  • Load balancing
  • Circuit Breakers
  • Distributed messaging

Part I. Cloud Native Applications

Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required.

Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul).

If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information:

Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using).

[Note]Note

Spring Cloud is released under the non-restrictive Apache 2.0 license. If you would like to contribute to this section of the documentation or if you find an error, please find the source code and issue trackers in the project at github.

2. Spring Cloud Context: Application Context Services

Spring Boot has an opinionated view of how to build an application with Spring: for instance it has conventional locations for common configuration file, and endpoints for common management and monitoring @@ -343,7 +343,7 @@ HTTP client and OkHttpClientConnectionPoolFactory f your own implementation of these beans if you would like to customize how the HTTP clients are created in downstream projects. You can also disable the creation of these beans by setting spring.cloud.httpclientfactories.apache.enabled or spring.cloud.httpclientfactories.ok.enabled to -false.

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
+false.

Part II. Spring Cloud Config

Edgware.SR1

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
 $ ../mvnw spring-boot:run

The server is a Spring Boot application so you can run it from your IDE instead if you prefer (the main class is ConfigServerApplication). Then try out a client:

$ curl localhost:8888/foo/development
@@ -1245,7 +1245,7 @@ in bootstrap.yml.
bootstrap.yml. 
       token: YourVaultToken

10.7 Vault

10.7.1 Nested Keys In Vault

Vault supports the ability to nest keys in a value stored in Vault. For example

echo -n '{"appA": {"secret": "appAsecret"}, "bar": "baz"}' | vault write secret/myapp -

This command will write a JSON object to your Vault. To access these values in Spring you would use the traditional dot(.) annotation. For example

@Value("${appA.secret}")
-String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration +String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

Edgware.SR1

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The @@ -4325,7 +4325,7 @@ package of BusConfiguration.

You can also exp }

All examples of @RemoteApplicationEventScan above are equivalent, in that the com.acme package will be registered by explicitly specifying the packages on @RemoteApplicationEventScan. Note, you can specify multiple base -packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

46. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

46.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an +packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Edgware.SR1

46. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

46.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an RPC. Span’s are identified by a unique 64-bit ID for the span and another 64-bit ID for the trace the span is a part of. Spans also have other data, such as descriptions, timestamped events, key-value annotations (tags), the ID of the span that caused them, and process ID’s (normally IP address).

Spans are started and stopped, and they keep track of their timing information. Once you create a @@ -5121,7 +5121,7 @@ subscribe events. To disable Spring Integration instrumentation, set

[Important]Important

When using the Executor to build a Spring Integration IntegrationFlow remember to use the untraced version of the Executor. Decorating Spring Integration Executor Channel with TraceableExecutorService will cause the spans to be improperly closed.

58.9 Zuul

We’re registering Zuul filters to propagate the tracing information (the request header is enriched with tracing data). -To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

59. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration +To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

59. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

Edgware.SR1

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The @@ -5605,7 +5605,7 @@ service called "sso", for instance, with credentials containing automatically to the Spring OAuth2 client that you enable with @EnableOAuth2Sso (from Spring Boot). The name of the service can be parameterized using spring.oauth2.sso.serviceId.

Part XII. Spring Cloud Contract

_Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

1.3.5.BUILD-SNAPSHOT

80. Spring Cloud Contract

You need confidence when pushing new features to a new application or service in a +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

Edgware.SR1

80. Spring Cloud Contract

You need confidence when pushing new features to a new application or service in a distributed system. This project provides support for Consumer Driven Contracts and service schemas in Spring applications (for both HTTP and message-based interactions), covering a range of options for writing tests, publishing them as assets, and asserting @@ -10510,7 +10510,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -10723,7 +10723,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -10740,7 +10740,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -10759,7 +10759,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) @@ -10786,7 +10786,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Edgware.SR1/spring-cloud.xml b/Edgware.SR1/spring-cloud.xml index f09248a7..af072e80 100644 --- a/Edgware.SR1/spring-cloud.xml +++ b/Edgware.SR1/spring-cloud.xml @@ -17,7 +17,7 @@ Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data centres, and managed platforms such as Cloud Foundry. -Version: 1.3.5.BUILD-SNAPSHOT +Version: Edgware.SR1 Features @@ -604,7 +604,7 @@ in downstream projects. You can also disable the creation of these beans by set Spring Cloud Config -1.3.5.BUILD-SNAPSHOT +Edgware.SR1 Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration. @@ -2095,7 +2095,7 @@ String name = "World"; Spring Cloud Netflix -1.3.5.BUILD-SNAPSHOT +Edgware.SR1 This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -8972,7 +8972,7 @@ packages to scan. Spring Cloud Sleuth Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer -1.3.5.BUILD-SNAPSHOT +Edgware.SR1 Introduction @@ -10676,7 +10676,7 @@ To disable Zuul support set the spring.sleuth.zuul.enabled pr Spring Cloud Consul -1.3.5.BUILD-SNAPSHOT +Edgware.SR1 This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -11751,7 +11751,7 @@ parameterized using spring.oauth2.sso.serviceId. _Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant -1.3.5.BUILD-SNAPSHOT +Edgware.SR1 Spring Cloud Contract @@ -19354,7 +19354,7 @@ the test cases). Example Maven configuration: <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -19926,7 +19926,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> </dependencies> @@ -19972,7 +19972,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> </dependencies> @@ -20023,7 +20023,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR1</version> </dependency> </dependencies> @@ -20099,7 +20099,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=database diff --git a/Edgware.SR2/multi/multi__client_side_usage_2.html b/Edgware.SR2/multi/multi__client_side_usage_2.html index d07210f7..607509e7 100644 --- a/Edgware.SR2/multi/multi__client_side_usage_2.html +++ b/Edgware.SR2/multi/multi__client_side_usage_2.html @@ -13,7 +13,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> diff --git a/Edgware.SR2/multi/multi__spring_cloud_config.html b/Edgware.SR2/multi/multi__spring_cloud_config.html index de19730e..d74719ae 100644 --- a/Edgware.SR2/multi/multi__spring_cloud_config.html +++ b/Edgware.SR2/multi/multi__spring_cloud_config.html @@ -1,3 +1,3 @@ - Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file + Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

Edgware.SR2

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file diff --git a/Edgware.SR2/multi/multi__spring_cloud_consul.html b/Edgware.SR2/multi/multi__spring_cloud_consul.html index d2837e7d..3a366c46 100644 --- a/Edgware.SR2/multi/multi__spring_cloud_consul.html +++ b/Edgware.SR2/multi/multi__spring_cloud_consul.html @@ -1,6 +1,6 @@ - Part VIII. Spring Cloud Consul
Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration + Part VIII. Spring Cloud Consul

Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

Edgware.SR2

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The diff --git a/Edgware.SR2/multi/multi__spring_cloud_contract.html b/Edgware.SR2/multi/multi__spring_cloud_contract.html index a1b4863c..2cc62f89 100644 --- a/Edgware.SR2/multi/multi__spring_cloud_contract.html +++ b/Edgware.SR2/multi/multi__spring_cloud_contract.html @@ -1,4 +1,4 @@ Part XII. Spring Cloud Contract

Part XII. Spring Cloud Contract
Prev   Next

Part XII. Spring Cloud Contract

_Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

1.3.5.BUILD-SNAPSHOT

Prev   Next
79. Single Sign On Home 80. Spring Cloud Contract
\ No newline at end of file +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

Edgware.SR2

Prev   Next
79. Single Sign On Home 80. Spring Cloud Contract
\ No newline at end of file diff --git a/Edgware.SR2/multi/multi__spring_cloud_netflix.html b/Edgware.SR2/multi/multi__spring_cloud_netflix.html index 874cb141..4bd5edcf 100644 --- a/Edgware.SR2/multi/multi__spring_cloud_netflix.html +++ b/Edgware.SR2/multi/multi__spring_cloud_netflix.html @@ -1,6 +1,6 @@ - Part III. Spring Cloud Netflix
Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration + Part III. Spring Cloud Netflix

Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

Edgware.SR2

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The diff --git a/Edgware.SR2/multi/multi__spring_cloud_sleuth.html b/Edgware.SR2/multi/multi__spring_cloud_sleuth.html index b42d45e1..373a6638 100644 --- a/Edgware.SR2/multi/multi__spring_cloud_sleuth.html +++ b/Edgware.SR2/multi/multi__spring_cloud_sleuth.html @@ -1,3 +1,3 @@ - Part VII. Spring Cloud Sleuth

Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

Prev   Next
45. Broadcasting Your Own Events Home 46. Introduction
\ No newline at end of file + Part VII. Spring Cloud Sleuth
Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Edgware.SR2

Prev   Next
45. Broadcasting Your Own Events Home 46. Introduction
\ No newline at end of file diff --git a/Edgware.SR2/multi/multi_pr01.html b/Edgware.SR2/multi/multi_pr01.html index c1944f54..2718f8ff 100644 --- a/Edgware.SR2/multi/multi_pr01.html +++ b/Edgware.SR2/multi/multi_pr01.html @@ -8,4 +8,4 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file +centres, and managed platforms such as Cloud Foundry.

Version: Edgware.SR2

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file diff --git a/Edgware.SR2/multi/multi_vault.config.backends.database-backends.html b/Edgware.SR2/multi/multi_vault.config.backends.database-backends.html index 5486754d..458c7180 100644 --- a/Edgware.SR2/multi/multi_vault.config.backends.database-backends.html +++ b/Edgware.SR2/multi/multi_vault.config.backends.database-backends.html @@ -13,7 +13,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Edgware.SR2/multi/multi_vault.config.backends.html b/Edgware.SR2/multi/multi_vault.config.backends.html index 8b42e532..40823ab9 100644 --- a/Edgware.SR2/multi/multi_vault.config.backends.html +++ b/Edgware.SR2/multi/multi_vault.config.backends.html @@ -26,7 +26,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -43,7 +43,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -62,7 +62,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/Edgware.SR2/single/spring-cloud.html b/Edgware.SR2/single/spring-cloud.html index 3926c2e2..c64de48c 100644 --- a/Edgware.SR2/single/spring-cloud.html +++ b/Edgware.SR2/single/spring-cloud.html @@ -8,7 +8,7 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases +centres, and managed platforms such as Cloud Foundry.

Version: Edgware.SR2

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases and extensibility mechanism to cover others.

  • Distributed/versioned configuration
  • Service registration and discovery
  • Routing
  • Service-to-service calls
  • Load balancing
  • Circuit Breakers
  • Distributed messaging

Part I. Cloud Native Applications

Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required.

Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul).

If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information:

Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using).

[Note]Note

Spring Cloud is released under the non-restrictive Apache 2.0 license. If you would like to contribute to this section of the documentation or if you find an error, please find the source code and issue trackers in the project at github.

2. Spring Cloud Context: Application Context Services

Spring Boot has an opinionated view of how to build an application with Spring: for instance it has conventional locations for common configuration file, and endpoints for common management and monitoring @@ -343,7 +343,7 @@ HTTP client and OkHttpClientConnectionPoolFactory f your own implementation of these beans if you would like to customize how the HTTP clients are created in downstream projects. You can also disable the creation of these beans by setting spring.cloud.httpclientfactories.apache.enabled or spring.cloud.httpclientfactories.ok.enabled to -false.

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
+false.

Part II. Spring Cloud Config

Edgware.SR2

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
 $ ../mvnw spring-boot:run

The server is a Spring Boot application so you can run it from your IDE instead if you prefer (the main class is ConfigServerApplication). Then try out a client:

$ curl localhost:8888/foo/development
@@ -1245,7 +1245,7 @@ in bootstrap.yml.
bootstrap.yml. 
       token: YourVaultToken

10.7 Vault

10.7.1 Nested Keys In Vault

Vault supports the ability to nest keys in a value stored in Vault. For example

echo -n '{"appA": {"secret": "appAsecret"}, "bar": "baz"}' | vault write secret/myapp -

This command will write a JSON object to your Vault. To access these values in Spring you would use the traditional dot(.) annotation. For example

@Value("${appA.secret}")
-String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration +String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

Edgware.SR2

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The @@ -4339,7 +4339,7 @@ package of BusConfiguration.

You can also exp }

All examples of @RemoteApplicationEventScan above are equivalent, in that the com.acme package will be registered by explicitly specifying the packages on @RemoteApplicationEventScan. Note, you can specify multiple base -packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

46. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

46.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an +packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Edgware.SR2

46. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

46.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an RPC. Span’s are identified by a unique 64-bit ID for the span and another 64-bit ID for the trace the span is a part of. Spans also have other data, such as descriptions, timestamped events, key-value annotations (tags), the ID of the span that caused them, and process ID’s (normally IP address).

Spans are started and stopped, and they keep track of their timing information. Once you create a @@ -5136,7 +5136,7 @@ subscribe events. To disable Spring Integration instrumentation, set

[Important]Important

When using the Executor to build a Spring Integration IntegrationFlow remember to use the untraced version of the Executor. Decorating Spring Integration Executor Channel with TraceableExecutorService will cause the spans to be improperly closed.

58.9 Zuul

We’re registering Zuul filters to propagate the tracing information (the request header is enriched with tracing data). -To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

59. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration +To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

59. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

Edgware.SR2

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The @@ -5620,7 +5620,7 @@ service called "sso", for instance, with credentials containing automatically to the Spring OAuth2 client that you enable with @EnableOAuth2Sso (from Spring Boot). The name of the service can be parameterized using spring.oauth2.sso.serviceId.

Part XII. Spring Cloud Contract

_Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

1.3.5.BUILD-SNAPSHOT

80. Spring Cloud Contract

You need confidence when pushing new features to a new application or service in a +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

Edgware.SR2

80. Spring Cloud Contract

You need confidence when pushing new features to a new application or service in a distributed system. This project provides support for Consumer Driven Contracts and service schemas in Spring applications (for both HTTP and message-based interactions), covering a range of options for writing tests, publishing them as assets, and asserting @@ -11160,7 +11160,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -11373,7 +11373,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -11390,7 +11390,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -11409,7 +11409,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) @@ -11436,7 +11436,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Edgware.SR2/spring-cloud.xml b/Edgware.SR2/spring-cloud.xml index 26d6f81c..163c773a 100644 --- a/Edgware.SR2/spring-cloud.xml +++ b/Edgware.SR2/spring-cloud.xml @@ -17,7 +17,7 @@ Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data centres, and managed platforms such as Cloud Foundry. -Version: 1.3.5.BUILD-SNAPSHOT +Version: Edgware.SR2 Features @@ -604,7 +604,7 @@ in downstream projects. You can also disable the creation of these beans by set Spring Cloud Config -1.3.5.BUILD-SNAPSHOT +Edgware.SR2 Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration. @@ -2095,7 +2095,7 @@ String name = "World"; Spring Cloud Netflix -1.3.5.BUILD-SNAPSHOT +Edgware.SR2 This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -9006,7 +9006,7 @@ packages to scan. Spring Cloud Sleuth Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer -1.3.5.BUILD-SNAPSHOT +Edgware.SR2 Introduction @@ -10711,7 +10711,7 @@ To disable Zuul support set the spring.sleuth.zuul.enabled pr Spring Cloud Consul -1.3.5.BUILD-SNAPSHOT +Edgware.SR2 This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -11786,7 +11786,7 @@ parameterized using spring.oauth2.sso.serviceId. _Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant -1.3.5.BUILD-SNAPSHOT +Edgware.SR2 Spring Cloud Contract @@ -20499,7 +20499,7 @@ the test cases). Example Maven configuration: <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -21071,7 +21071,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> </dependencies> @@ -21117,7 +21117,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> </dependencies> @@ -21168,7 +21168,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Edgware.SR2</version> </dependency> </dependencies> @@ -21244,7 +21244,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=database diff --git a/Finchley.M5/index.html b/Finchley.M5/index.html index 6b5b9e65..5ea3fcef 100644 --- a/Finchley.M5/index.html +++ b/Finchley.M5/index.html @@ -90,7 +90,7 @@ $(addBlockSwitches);

-

1.3.5.BUILD-SNAPSHOT

+

Finchley.M5

diff --git a/Finchley.M5/multi/multi__client_side_usage_2.html b/Finchley.M5/multi/multi__client_side_usage_2.html index e52ed469..feadae0f 100644 --- a/Finchley.M5/multi/multi__client_side_usage_2.html +++ b/Finchley.M5/multi/multi__client_side_usage_2.html @@ -13,7 +13,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> diff --git a/Finchley.M5/multi/multi__spring_cloud_config.html b/Finchley.M5/multi/multi__spring_cloud_config.html index de19730e..6aaf91fe 100644 --- a/Finchley.M5/multi/multi__spring_cloud_config.html +++ b/Finchley.M5/multi/multi__spring_cloud_config.html @@ -1,3 +1,3 @@ - Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file + Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

Finchley.M5

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file diff --git a/Finchley.M5/multi/multi__spring_cloud_consul.html b/Finchley.M5/multi/multi__spring_cloud_consul.html index 54e4b0b1..70fcb657 100644 --- a/Finchley.M5/multi/multi__spring_cloud_consul.html +++ b/Finchley.M5/multi/multi__spring_cloud_consul.html @@ -1,6 +1,6 @@ - Part VIII. Spring Cloud Consul
Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration + Part VIII. Spring Cloud Consul

Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

Finchley.M5

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The diff --git a/Finchley.M5/multi/multi__spring_cloud_contract.html b/Finchley.M5/multi/multi__spring_cloud_contract.html index 427e4f0e..43bf9e48 100644 --- a/Finchley.M5/multi/multi__spring_cloud_contract.html +++ b/Finchley.M5/multi/multi__spring_cloud_contract.html @@ -1,4 +1,4 @@ Part XII. Spring Cloud Contract

Part XII. Spring Cloud Contract
Prev   Next

Part XII. Spring Cloud Contract

_Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

1.3.5.BUILD-SNAPSHOT

Prev   Next
78. Single Sign On Home 79. Spring Cloud Contract
\ No newline at end of file +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

Finchley.M5

Prev   Next
78. Single Sign On Home 79. Spring Cloud Contract
\ No newline at end of file diff --git a/Finchley.M5/multi/multi__spring_cloud_netflix.html b/Finchley.M5/multi/multi__spring_cloud_netflix.html index 874cb141..3efd6075 100644 --- a/Finchley.M5/multi/multi__spring_cloud_netflix.html +++ b/Finchley.M5/multi/multi__spring_cloud_netflix.html @@ -1,6 +1,6 @@ - Part III. Spring Cloud Netflix
Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration + Part III. Spring Cloud Netflix

Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

Finchley.M5

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The diff --git a/Finchley.M5/multi/multi__spring_cloud_sleuth.html b/Finchley.M5/multi/multi__spring_cloud_sleuth.html index cd824b23..d4fb7ae3 100644 --- a/Finchley.M5/multi/multi__spring_cloud_sleuth.html +++ b/Finchley.M5/multi/multi__spring_cloud_sleuth.html @@ -1,3 +1,3 @@ - Part VII. Spring Cloud Sleuth

Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

Prev   Next
44. Broadcasting Your Own Events Home 45. Introduction
\ No newline at end of file + Part VII. Spring Cloud Sleuth
Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Finchley.M5

Prev   Next
44. Broadcasting Your Own Events Home 45. Introduction
\ No newline at end of file diff --git a/Finchley.M5/multi/multi_pr01.html b/Finchley.M5/multi/multi_pr01.html index c1944f54..2810b221 100644 --- a/Finchley.M5/multi/multi_pr01.html +++ b/Finchley.M5/multi/multi_pr01.html @@ -8,4 +8,4 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file +centres, and managed platforms such as Cloud Foundry.

Version: Finchley.M5

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file diff --git a/Finchley.M5/multi/multi_vault.config.backends.database-backends.html b/Finchley.M5/multi/multi_vault.config.backends.database-backends.html index 1bcfb663..4664b543 100644 --- a/Finchley.M5/multi/multi_vault.config.backends.database-backends.html +++ b/Finchley.M5/multi/multi_vault.config.backends.database-backends.html @@ -13,7 +13,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Finchley.M5/multi/multi_vault.config.backends.html b/Finchley.M5/multi/multi_vault.config.backends.html index 6c1af16d..7ae285ea 100644 --- a/Finchley.M5/multi/multi_vault.config.backends.html +++ b/Finchley.M5/multi/multi_vault.config.backends.html @@ -26,7 +26,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -43,7 +43,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -62,7 +62,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/Finchley.M5/single/spring-cloud.html b/Finchley.M5/single/spring-cloud.html index 3aea5e20..61f135a3 100644 --- a/Finchley.M5/single/spring-cloud.html +++ b/Finchley.M5/single/spring-cloud.html @@ -8,7 +8,7 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases +centres, and managed platforms such as Cloud Foundry.

Version: Finchley.M5

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases and extensibility mechanism to cover others.

  • Distributed/versioned configuration
  • Service registration and discovery
  • Routing
  • Service-to-service calls
  • Load balancing
  • Circuit Breakers
  • Distributed messaging

Part I. Cloud Native Applications

Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required.

Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul).

If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information:

Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using).

[Note]Note

Spring Cloud is released under the non-restrictive Apache 2.0 license. If you would like to contribute to this section of the documentation or if you find an error, please find the source code and issue trackers in the project at github.

2. Spring Cloud Context: Application Context Services

Spring Boot has an opinionated view of how to build an application with Spring: for instance it has conventional locations for common configuration file, and endpoints for common management and monitoring @@ -328,7 +328,7 @@ HTTP client and OkHttpClientConnectionPoolFactory f your own implementation of these beans if you would like to customize how the HTTP clients are created in downstream projects. You can also disable the creation of these beans by setting spring.cloud.httpclientfactories.apache.enabled or spring.cloud.httpclientfactories.ok.enabled to -false.

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
+false.

Part II. Spring Cloud Config

Finchley.M5

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
 $ ../mvnw spring-boot:run

The server is a Spring Boot application so you can run it from your IDE instead if you prefer (the main class is ConfigServerApplication). Then try out a client:

$ curl localhost:8888/foo/development
@@ -1230,7 +1230,7 @@ in bootstrap.yml.
bootstrap.yml. 
       token: YourVaultToken

10.7 Vault

10.7.1 Nested Keys In Vault

Vault supports the ability to nest keys in a value stored in Vault. For example

echo -n '{"appA": {"secret": "appAsecret"}, "bar": "baz"}' | vault write secret/myapp -

This command will write a JSON object to your Vault. To access these values in Spring you would use the traditional dot(.) annotation. For example

@Value("${appA.secret}")
-String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration +String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

Finchley.M5

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The @@ -4255,7 +4255,7 @@ package of BusConfiguration.

You can also exp }

All examples of @RemoteApplicationEventScan above are equivalent, in that the com.acme package will be registered by explicitly specifying the packages on @RemoteApplicationEventScan. Note, you can specify multiple base -packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

45. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

45.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an +packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Finchley.M5

45. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

45.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an RPC. Span’s are identified by a unique 64-bit ID for the span and another 64-bit ID for the trace the span is a part of. Spans also have other data, such as descriptions, timestamped events, key-value annotations (tags), the ID of the span that caused them, and process ID’s (normally IP address).

Spans are started and stopped, and they keep track of their timing information. Once you create a @@ -5026,7 +5026,7 @@ subscribe events. To disable Spring Integration instrumentation, set

[Important]Important

When using the Executor to build a Spring Integration IntegrationFlow remember to use the untraced version of the Executor. Decorating Spring Integration Executor Channel with TraceableExecutorService will cause the spans to be improperly closed.

57.9 Zuul

We’re registering Zuul filters to propagate the tracing information (the request header is enriched with tracing data). -To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

58. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration +To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

58. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

Finchley.M5

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The @@ -5510,7 +5510,7 @@ service called "sso", for instance, with credentials containing automatically to the Spring OAuth2 client that you enable with @EnableOAuth2Sso (from Spring Boot). The name of the service can be parameterized using spring.oauth2.sso.serviceId.

Part XII. Spring Cloud Contract

_Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

1.3.5.BUILD-SNAPSHOT

79. Spring Cloud Contract

You need confidence when pushing new features to a new application or service in a +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

Finchley.M5

79. Spring Cloud Contract

You need confidence when pushing new features to a new application or service in a distributed system. This project provides support for Consumer Driven Contracts and service schemas in Spring applications (for both HTTP and message-based interactions), covering a range of options for writing tests, publishing them as assets, and asserting @@ -10345,7 +10345,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -10558,7 +10558,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -10575,7 +10575,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -10594,7 +10594,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) @@ -10621,7 +10621,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Finchley.M5/spring-cloud.xml b/Finchley.M5/spring-cloud.xml index a6a902a4..b53bb0d0 100644 --- a/Finchley.M5/spring-cloud.xml +++ b/Finchley.M5/spring-cloud.xml @@ -17,7 +17,7 @@ Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data centres, and managed platforms such as Cloud Foundry. -Version: 1.3.5.BUILD-SNAPSHOT +Version: Finchley.M5 Features @@ -593,7 +593,7 @@ in downstream projects. You can also disable the creation of these beans by set Spring Cloud Config -1.3.5.BUILD-SNAPSHOT +Finchley.M5 Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration. @@ -2084,7 +2084,7 @@ String name = "World"; Spring Cloud Netflix -1.3.5.BUILD-SNAPSHOT +Finchley.M5 This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -8941,7 +8941,7 @@ packages to scan. Spring Cloud Sleuth Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer -1.3.5.BUILD-SNAPSHOT +Finchley.M5 Introduction @@ -10625,7 +10625,7 @@ To disable Zuul support set the spring.sleuth.zuul.enabled pr Spring Cloud Consul -1.3.5.BUILD-SNAPSHOT +Finchley.M5 This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your @@ -11700,7 +11700,7 @@ parameterized using spring.oauth2.sso.serviceId. _Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant -1.3.5.BUILD-SNAPSHOT +Finchley.M5 Spring Cloud Contract @@ -19177,7 +19177,7 @@ the test cases). Example Maven configuration: <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -19749,7 +19749,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> </dependencies> @@ -19795,7 +19795,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> </dependencies> @@ -19846,7 +19846,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M5</version> </dependency> </dependencies> @@ -19925,7 +19925,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=database diff --git a/Finchley.M6/index.html b/Finchley.M6/index.html index 6b5b9e65..5c5c9307 100644 --- a/Finchley.M6/index.html +++ b/Finchley.M6/index.html @@ -90,7 +90,7 @@ $(addBlockSwitches);

-

1.3.5.BUILD-SNAPSHOT

+

Finchley.M6

diff --git a/Finchley.M6/multi/multi__client_side_usage_2.html b/Finchley.M6/multi/multi__client_side_usage_2.html index 83fc0227..2439fa38 100644 --- a/Finchley.M6/multi/multi__client_side_usage_2.html +++ b/Finchley.M6/multi/multi__client_side_usage_2.html @@ -13,7 +13,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M6</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> diff --git a/Finchley.M6/multi/multi__spring_cloud_config.html b/Finchley.M6/multi/multi__spring_cloud_config.html index de19730e..5bdc31c5 100644 --- a/Finchley.M6/multi/multi__spring_cloud_config.html +++ b/Finchley.M6/multi/multi__spring_cloud_config.html @@ -1,3 +1,3 @@ - Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file + Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

Finchley.M6

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

Prev   Next
3. Spring Cloud Commons: Common Abstractions Home 4. Quick Start
\ No newline at end of file diff --git a/Finchley.M6/multi/multi__spring_cloud_consul.html b/Finchley.M6/multi/multi__spring_cloud_consul.html index 086de519..5dee7b61 100644 --- a/Finchley.M6/multi/multi__spring_cloud_consul.html +++ b/Finchley.M6/multi/multi__spring_cloud_consul.html @@ -1,6 +1,6 @@ - Part VIII. Spring Cloud Consul
Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration + Part VIII. Spring Cloud Consul

Part VIII. Spring Cloud Consul
Prev   Next

Part VIII. Spring Cloud Consul

Finchley.M6

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The diff --git a/Finchley.M6/multi/multi__spring_cloud_contract.html b/Finchley.M6/multi/multi__spring_cloud_contract.html index cb1caea2..c1166082 100644 --- a/Finchley.M6/multi/multi__spring_cloud_contract.html +++ b/Finchley.M6/multi/multi__spring_cloud_contract.html @@ -1,4 +1,4 @@ Part XII. Spring Cloud Contract

Part XII. Spring Cloud Contract
Prev   Next

Part XII. Spring Cloud Contract

_Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

1.3.5.BUILD-SNAPSHOT

Prev   Next
80. Single Sign On Home 81. Spring Cloud Contract
\ No newline at end of file +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

Finchley.M6

Prev   Next
80. Single Sign On Home 81. Spring Cloud Contract
\ No newline at end of file diff --git a/Finchley.M6/multi/multi__spring_cloud_gateway.html b/Finchley.M6/multi/multi__spring_cloud_gateway.html index d80e80a6..a85c41d6 100644 --- a/Finchley.M6/multi/multi__spring_cloud_gateway.html +++ b/Finchley.M6/multi/multi__spring_cloud_gateway.html @@ -1,3 +1,3 @@ - Part XIV. Spring Cloud Gateway
Part XIV. Spring Cloud Gateway
Prev   Next

Part XIV. Spring Cloud Gateway

1.3.5.BUILD-SNAPSHOT

This project provides an API Gateway built on top of the Spring Ecosystem, including: Spring 5, Spring Boot 2 and Project Reactor. Spring Cloud Gateway aims to provide a simple, yet effective way to route to APIs and provide cross cutting concerns to them such as: security, monitoring/metrics, and resiliency.

Prev   Next
103. Lease lifecycle management (renewal and revocation) Home 104. How to Include Spring Cloud Gateway
\ No newline at end of file + Part XIV. Spring Cloud Gateway
Part XIV. Spring Cloud Gateway
Prev   Next

Part XIV. Spring Cloud Gateway

Finchley.M6

This project provides an API Gateway built on top of the Spring Ecosystem, including: Spring 5, Spring Boot 2 and Project Reactor. Spring Cloud Gateway aims to provide a simple, yet effective way to route to APIs and provide cross cutting concerns to them such as: security, monitoring/metrics, and resiliency.

Prev   Next
103. Lease lifecycle management (renewal and revocation) Home 104. How to Include Spring Cloud Gateway
\ No newline at end of file diff --git a/Finchley.M6/multi/multi__spring_cloud_netflix.html b/Finchley.M6/multi/multi__spring_cloud_netflix.html index 874cb141..0d0ca48d 100644 --- a/Finchley.M6/multi/multi__spring_cloud_netflix.html +++ b/Finchley.M6/multi/multi__spring_cloud_netflix.html @@ -1,6 +1,6 @@ - Part III. Spring Cloud Netflix
Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration + Part III. Spring Cloud Netflix

Part III. Spring Cloud Netflix
Prev   Next

Part III. Spring Cloud Netflix

Finchley.M6

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The diff --git a/Finchley.M6/multi/multi__spring_cloud_sleuth.html b/Finchley.M6/multi/multi__spring_cloud_sleuth.html index cd824b23..83f77798 100644 --- a/Finchley.M6/multi/multi__spring_cloud_sleuth.html +++ b/Finchley.M6/multi/multi__spring_cloud_sleuth.html @@ -1,3 +1,3 @@ - Part VII. Spring Cloud Sleuth

Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

Prev   Next
44. Broadcasting Your Own Events Home 45. Introduction
\ No newline at end of file + Part VII. Spring Cloud Sleuth
Part VII. Spring Cloud Sleuth
Prev   Next

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Finchley.M6

Prev   Next
44. Broadcasting Your Own Events Home 45. Introduction
\ No newline at end of file diff --git a/Finchley.M6/multi/multi_pr01.html b/Finchley.M6/multi/multi_pr01.html index c1944f54..0455219f 100644 --- a/Finchley.M6/multi/multi_pr01.html +++ b/Finchley.M6/multi/multi_pr01.html @@ -8,4 +8,4 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file +centres, and managed platforms such as Cloud Foundry.

Version: Finchley.M6

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file diff --git a/Finchley.M6/multi/multi_vault.config.backends.database-backends.html b/Finchley.M6/multi/multi_vault.config.backends.database-backends.html index cdad5f36..db3dcf0a 100644 --- a/Finchley.M6/multi/multi_vault.config.backends.database-backends.html +++ b/Finchley.M6/multi/multi_vault.config.backends.database-backends.html @@ -13,7 +13,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M6</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/Finchley.M6/multi/multi_vault.config.backends.html b/Finchley.M6/multi/multi_vault.config.backends.html index ab9caee2..b97a7567 100644 --- a/Finchley.M6/multi/multi_vault.config.backends.html +++ b/Finchley.M6/multi/multi_vault.config.backends.html @@ -26,7 +26,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M6</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -43,7 +43,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M6</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -62,7 +62,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M6</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/Finchley.M6/single/spring-cloud.html b/Finchley.M6/single/spring-cloud.html index a0b674ec..e116d583 100644 --- a/Finchley.M6/single/spring-cloud.html +++ b/Finchley.M6/single/spring-cloud.html @@ -8,7 +8,7 @@ distributed systems leads to boiler plate patterns, and using Spring Cloud developers can quickly stand up services and applications that implement those patterns. They will work well in any distributed environment, including the developer’s own laptop, bare metal data -centres, and managed platforms such as Cloud Foundry.

Version: 1.3.5.BUILD-SNAPSHOT

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases +centres, and managed platforms such as Cloud Foundry.

Version: Finchley.M6

1. Features

Spring Cloud focuses on providing good out of box experience for typical use cases and extensibility mechanism to cover others.

  • Distributed/versioned configuration
  • Service registration and discovery
  • Routing
  • Service-to-service calls
  • Load balancing
  • Circuit Breakers
  • Distributed messaging

Part I. Cloud Native Applications

Cloud Native is a style of application development that encourages easy adoption of best practices in the areas of continuous delivery and value-driven development. A related discipline is that of building 12-factor Apps in which development practices are aligned with delivery and operations goals, for instance by using declarative programming and management and monitoring. Spring Cloud facilitates these styles of development in a number of specific ways and the starting point is a set of features that all components in a distributed system either need or need easy access to when required.

Many of those features are covered by Spring Boot, which we build on in Spring Cloud. Some more are delivered by Spring Cloud as two libraries: Spring Cloud Context and Spring Cloud Commons. Spring Cloud Context provides utilities and special services for the ApplicationContext of a Spring Cloud application (bootstrap context, encryption, refresh scope and environment endpoints). Spring Cloud Commons is a set of abstractions and common classes used in different Spring Cloud implementations (eg. Spring Cloud Netflix vs. Spring Cloud Consul).

If you are getting an exception due to "Illegal key size" and you are using Sun’s JDK, you need to install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. See the following links for more information:

Extract files into JDK/jre/lib/security folder (whichever version of JRE/JDK x64/x86 you are using).

[Note]Note

Spring Cloud is released under the non-restrictive Apache 2.0 license. If you would like to contribute to this section of the documentation or if you find an error, please find the source code and issue trackers in the project at github.

2. Spring Cloud Context: Application Context Services

Spring Boot has an opinionated view of how to build an application with Spring: for instance it has conventional locations for common configuration file, and endpoints for common management and monitoring @@ -397,7 +397,7 @@ HasFeatures localFeatures() { .namedFeature(new NamedFeature("Bar Feature", Bar.class)) .abstractFeature(Baz.class) .build(); -}

Each of these beans should go in an appropriately guarded @Configuration.

Part II. Spring Cloud Config

1.3.5.BUILD-SNAPSHOT

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
+}

Each of these beans should go in an appropriately guarded @Configuration.

Part II. Spring Cloud Config

Finchley.M6

Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations and plug them in with Spring configuration.

4. Quick Start

Start the server:

$ cd spring-cloud-config-server
 $ ../mvnw spring-boot:run

The server is a Spring Boot application so you can run it from your IDE instead if you prefer (the main class is ConfigServerApplication). Then try out a client:

$ curl localhost:8888/foo/development
@@ -1299,7 +1299,7 @@ in bootstrap.yml.
bootstrap.yml. 
       token: YourVaultToken

10.7 Vault

10.7.1 Nested Keys In Vault

Vault supports the ability to nest keys in a value stored in Vault. For example

echo -n '{"appA": {"secret": "appAsecret"}, "bar": "baz"}' | vault write secret/myapp -

This command will write a JSON object to your Vault. To access these values in Spring you would use the traditional dot(.) annotation. For example

@Value("${appA.secret}")
-String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

1.3.5.BUILD-SNAPSHOT

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration +String name = "World";

The above code would set the name variable to appAsecret.

Part III. Spring Cloud Netflix

Finchley.M6

This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with battle-tested Netflix components. The @@ -4603,7 +4603,7 @@ package of BusConfiguration.

You can also exp }

All examples of @RemoteApplicationEventScan above are equivalent, in that the com.acme package will be registered by explicitly specifying the packages on @RemoteApplicationEventScan. Note, you can specify multiple base -packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

1.3.5.BUILD-SNAPSHOT

45. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

45.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an +packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Finchley.M6

45. Introduction

Spring Cloud Sleuth implements a distributed tracing solution for Spring Cloud.

45.1 Terminology

Spring Cloud Sleuth borrows Dapper’s terminology.

Span: The basic unit of work. For example, sending an RPC is a new span, as is sending a response to an RPC. Span’s are identified by a unique 64-bit ID for the span and another 64-bit ID for the trace the span is a part of. Spans also have other data, such as descriptions, timestamped events, key-value annotations (tags), the ID of the span that caused them, and process ID’s (normally IP address).

Spans are started and stopped, and they keep track of their timing information. Once you create a @@ -5462,7 +5462,7 @@ subscribe events. To disable Spring Integration instrumentation, set

[Important]Important

When using the Executor to build a Spring Integration IntegrationFlow remember to use the untraced version of the Executor. Decorating Spring Integration Executor Channel with TraceableExecutorService will cause the spans to be improperly closed.

59.10 Zuul

We’re instrumenting the Zuul Ribbon integration by enriching the Ribbon requests with tracing information. -To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

60. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

1.3.5.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration +To disable Zuul support set the spring.sleuth.zuul.enabled property to false.

60. Running examples

You can find the running examples deployed in the Pivotal Web Services. Check them out in the following links:

Part VIII. Spring Cloud Consul

Finchley.M6

This project provides Consul integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms. With a few simple annotations you can quickly enable and configure the common patterns inside your application and build large distributed systems with Consul based components. The @@ -5943,7 +5943,7 @@ service called "sso", for instance, with credentials containing automatically to the Spring OAuth2 client that you enable with @EnableOAuth2Sso (from Spring Boot). The name of the service can be parameterized using spring.oauth2.sso.serviceId.

Part XII. Spring Cloud Contract

_Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak, -Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

1.3.5.BUILD-SNAPSHOT

81. Spring Cloud Contract

You need confidence when pushing new features to a new application or service in a +Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant

Finchley.M6

81. Spring Cloud Contract

You need confidence when pushing new features to a new application or service in a distributed system. This project provides support for Consumer Driven Contracts and service schemas in Spring applications (for both HTTP and message-based interactions), covering a range of options for writing tests, publishing them as assets, and asserting @@ -11443,7 +11443,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M6</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -11656,7 +11656,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M6</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -11673,7 +11673,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M6</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -11692,7 +11692,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M6</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) @@ -11719,7 +11719,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.3.5.BUILD-SNAPSHOT</version> + <version>Finchley.M6</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for @@ -11869,7 +11869,7 @@ to false. This is not recommended as leases can exp Spring Cloud Vault cannot longer access Vault or services using generated credentials and valid credentials remain active after application shutdown.

spring.cloud.vault:
-    config.lifecycle.enabled: true

See also: Vault Documentation: Lease, Renew, and Revoke

Part XIV. Spring Cloud Gateway

1.3.5.BUILD-SNAPSHOT

This project provides an API Gateway built on top of the Spring Ecosystem, including: Spring 5, Spring Boot 2 and Project Reactor. Spring Cloud Gateway aims to provide a simple, yet effective way to route to APIs and provide cross cutting concerns to them such as: security, monitoring/metrics, and resiliency.

104. How to Include Spring Cloud Gateway

To include Spring Cloud Gateway in your project use the starter with group org.springframework.cloud + config.lifecycle.enabled: true

See also: Vault Documentation: Lease, Renew, and Revoke

Part XIV. Spring Cloud Gateway

Finchley.M6

This project provides an API Gateway built on top of the Spring Ecosystem, including: Spring 5, Spring Boot 2 and Project Reactor. Spring Cloud Gateway aims to provide a simple, yet effective way to route to APIs and provide cross cutting concerns to them such as: security, monitoring/metrics, and resiliency.

104. How to Include Spring Cloud Gateway

To include Spring Cloud Gateway in your project use the starter with group org.springframework.cloud and artifact id spring-cloud-starter-gateway. See the Spring Cloud Project page for details on setting up your build system with the current Spring Cloud Release Train.

If you include the starter, but, for some reason, you do not want the gateway to be enabled, set spring.cloud.gateway.enabled=false.

105. Glossary

  • Route: Route the basic building block of the gateway. It is defined by an ID, a destination URI, a collection of predicates and a collection of filters. A route is matched if aggregate predicate is true.
  • Predicate: This is a Java 8 Function Predicate. The input type is a Spring Framework ServerWebExchange. This allows developers to match on anything from the HTTP request, such as headers or parameters.
  • Filter: These are instances Spring Framework GatewayFilter constructed in with a specific factory. Here, requests and responses can be modified before or after sending the downstream request.

106. How It Works

Spring Cloud Gateway Diagram

Clients make requests to Spring Cloud Gateway. If the Gateway Handler Mapping determines that a request matches a Route, it is sent to the Gateway Web Handler. This handler runs sends the request through a filter chain that is specific to the request. The reason the filters are divided by the dotted line, is that filters may execute logic before the proxy request is sent or after. All "pre" filter logic is executed, then the proxy request is made. After the proxy request is made, the "post" filter logic is executed.

107. Route Predicate Factories

Spring Cloud Gateway matches routes as part of the Spring WebFlux HandlerMapping infrastructure. Spring Cloud Gateway includes many built-in Route Predicate Factories. All of these predicates match on different attributes of the HTTP request. Multiple Route Predicate Factories can be combined and are combined via logical and.

107.1 After Route Predicate Factory

The After Route Predicate Factory takes one parameter, a datetime. This predicate matches requests that happen after the current datetime.

application.yml.  

spring:
diff --git a/Finchley.M6/spring-cloud.xml b/Finchley.M6/spring-cloud.xml
index 1a1a080b..5255e185 100644
--- a/Finchley.M6/spring-cloud.xml
+++ b/Finchley.M6/spring-cloud.xml
@@ -17,7 +17,7 @@ Cloud developers can quickly stand up services and applications that
 implement those patterns. They will work well in any distributed
 environment, including the developer’s own laptop, bare metal data
 centres, and managed platforms such as Cloud Foundry.
-Version: 1.3.5.BUILD-SNAPSHOT
+Version: Finchley.M6
 
 
 Features
@@ -686,7 +686,7 @@ HasFeatures localFeatures() {
 
 Spring Cloud Config
 
-1.3.5.BUILD-SNAPSHOT
+Finchley.M6
 Spring Cloud Config provides server and client-side support for externalized configuration in a distributed system. With the Config Server you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications, but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git so it easily supports labelled versions of configuration environments, as well as being accessible to a wide range of tooling for managing the content.  It is easy to add alternative implementations and plug them in with Spring configuration.
 
 
@@ -2177,7 +2177,7 @@ String name = "World";
 
 Spring Cloud Netflix
 
-1.3.5.BUILD-SNAPSHOT
+Finchley.M6
 This project provides Netflix OSS integrations for Spring Boot apps through autoconfiguration
 and binding to the Spring Environment and other Spring programming model idioms. With a few
 simple annotations you can quickly enable and configure the common patterns inside your
@@ -9505,7 +9505,7 @@ packages to scan.
 Spring Cloud Sleuth
 
 Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer
-1.3.5.BUILD-SNAPSHOT
+Finchley.M6
 
 
 Introduction
@@ -11357,7 +11357,7 @@ To disable Zuul support set the spring.sleuth.zuul.enabled pr
 
 Spring Cloud Consul
 
-1.3.5.BUILD-SNAPSHOT
+Finchley.M6
 This project provides Consul integrations for Spring Boot apps through autoconfiguration
 and binding to the Spring Environment and other Spring programming model idioms. With a few
 simple annotations you can quickly enable and configure the common patterns inside your
@@ -12430,7 +12430,7 @@ parameterized using spring.oauth2.sso.serviceId.
 
 _Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak,
 Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant
-1.3.5.BUILD-SNAPSHOT
+Finchley.M6
 
 
 Spring Cloud Contract
@@ -21065,7 +21065,7 @@ the test cases). Example Maven configuration:
     <dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-starter-vault-config</artifactId>
-        <version>1.3.5.BUILD-SNAPSHOT</version>
+        <version>Finchley.M6</version>
     </dependency>
     <dependency>
         <groupId>org.springframework.boot</groupId>
@@ -21789,7 +21789,7 @@ dependency.
     <dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-vault-config-consul</artifactId>
-        <version>1.3.5.BUILD-SNAPSHOT</version>
+        <version>Finchley.M6</version>
     </dependency>
 </dependencies>
 
@@ -21835,7 +21835,7 @@ dependency.
     <dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-vault-config-rabbitmq</artifactId>
-        <version>1.3.5.BUILD-SNAPSHOT</version>
+        <version>Finchley.M6</version>
     </dependency>
 </dependencies>
 
@@ -21886,7 +21886,7 @@ dependency.
     <dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-vault-config-aws</artifactId>
-        <version>1.3.5.BUILD-SNAPSHOT</version>
+        <version>Finchley.M6</version>
     </dependency>
 </dependencies>
 
@@ -21965,7 +21965,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=database
 
@@ -22326,7 +22326,7 @@ after application shutdown.
 
 Spring Cloud Gateway
 
-1.3.5.BUILD-SNAPSHOT
+Finchley.M6
 This project provides an API Gateway built on top of the Spring Ecosystem, including: Spring 5, Spring Boot 2 and Project Reactor. Spring Cloud Gateway aims to provide a simple, yet effective way to route to APIs and provide cross cutting concerns to them such as: security, monitoring/metrics, and resiliency.