diff --git a/Edgware.SR4/index.html b/Edgware.SR4/index.html index 7bcb249b..55242de5 100644 --- a/Edgware.SR4/index.html +++ b/Edgware.SR4/index.html @@ -90,7 +90,7 @@ $(addBlockSwitches);
-

1.3.8.RELEASE

+

Edgware.SR4

diff --git a/Edgware.SR4/multi/multi__client_side_usage_2.html b/Edgware.SR4/multi/multi__client_side_usage_2.html index 8eae3628..e76a8088 100644 --- a/Edgware.SR4/multi/multi__client_side_usage_2.html +++ b/Edgware.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.8.RELEASE</version> + <version>Edgware.SR4</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> diff --git a/Edgware.SR4/multi/multi__spring_cloud_config.html b/Edgware.SR4/multi/multi__spring_cloud_config.html index 2ea3f227..f50a728e 100644 --- a/Edgware.SR4/multi/multi__spring_cloud_config.html +++ b/Edgware.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.8.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 + Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

Edgware.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/Edgware.SR4/multi/multi__spring_cloud_consul.html b/Edgware.SR4/multi/multi__spring_cloud_consul.html index 2f67f582..46d029b9 100644 --- a/Edgware.SR4/multi/multi__spring_cloud_consul.html +++ b/Edgware.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.8.RELEASE

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.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/Edgware.SR4/multi/multi__spring_cloud_contract.html b/Edgware.SR4/multi/multi__spring_cloud_contract.html index e1d957da..e1e7ea06 100644 --- a/Edgware.SR4/multi/multi__spring_cloud_contract.html +++ b/Edgware.SR4/multi/multi__spring_cloud_contract.html @@ -1,4 +1,4 @@ Part XIII. Spring Cloud Contract

Part XIII. Spring Cloud Contract
Prev   Next

Part XIII. 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.8.RELEASE

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

Edgware.SR4

Prev   Next
83. Single Sign On Home 84. Spring Cloud Contract
\ No newline at end of file diff --git a/Edgware.SR4/multi/multi__spring_cloud_netflix.html b/Edgware.SR4/multi/multi__spring_cloud_netflix.html index 1041d3db..961ee566 100644 --- a/Edgware.SR4/multi/multi__spring_cloud_netflix.html +++ b/Edgware.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.8.RELEASE

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.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/Edgware.SR4/multi/multi__spring_cloud_sleuth.html b/Edgware.SR4/multi/multi__spring_cloud_sleuth.html index 81b43737..3c949f0e 100644 --- a/Edgware.SR4/multi/multi__spring_cloud_sleuth.html +++ b/Edgware.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.8.RELEASE

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.SR4

Prev   Next
45. Broadcasting Your Own Events Home 46. Introduction
\ No newline at end of file diff --git a/Edgware.SR4/multi/multi_pr01.html b/Edgware.SR4/multi/multi_pr01.html index 826b67cb..73ec5bcd 100644 --- a/Edgware.SR4/multi/multi_pr01.html +++ b/Edgware.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.8.RELEASE

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

Version: Edgware.SR4

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file diff --git a/Edgware.SR4/multi/multi_vault.config.backends.database-backends.html b/Edgware.SR4/multi/multi_vault.config.backends.database-backends.html index 6faefbb6..d30caf90 100644 --- a/Edgware.SR4/multi/multi_vault.config.backends.database-backends.html +++ b/Edgware.SR4/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.8.RELEASE</version> + <version>Edgware.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/Edgware.SR4/multi/multi_vault.config.backends.html b/Edgware.SR4/multi/multi_vault.config.backends.html index a804aef5..69a4c8ca 100644 --- a/Edgware.SR4/multi/multi_vault.config.backends.html +++ b/Edgware.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.8.RELEASE</version> + <version>Edgware.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.8.RELEASE</version> + <version>Edgware.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.8.RELEASE</version> + <version>Edgware.SR4</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/Edgware.SR4/spring-cloud.xml b/Edgware.SR4/spring-cloud.xml index e59441ae..f95c2b82 100644 --- a/Edgware.SR4/spring-cloud.xml +++ b/Edgware.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.8.RELEASE +Version: Edgware.SR4 Features @@ -629,7 +629,7 @@ in downstream projects. You can also disable the creation of these beans by set Spring Cloud Config -1.3.8.RELEASE +Edgware.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. @@ -2150,7 +2150,7 @@ String name = "World"; Spring Cloud Netflix -1.3.8.RELEASE +Edgware.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 @@ -9098,7 +9098,7 @@ packages to scan. Spring Cloud Sleuth Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer -1.3.8.RELEASE +Edgware.SR4 Introduction @@ -10878,7 +10878,7 @@ class ReporterConfiguration { Spring Cloud Consul -1.3.8.RELEASE +Edgware.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 @@ -12164,7 +12164,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.8.RELEASE +Edgware.SR4 Spring Cloud Contract @@ -20940,7 +20940,7 @@ the test cases). Example Maven configuration: <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.8.RELEASE</version> + <version>Edgware.SR4</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -21512,7 +21512,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.8.RELEASE</version> + <version>Edgware.SR4</version> </dependency> </dependencies> @@ -21558,7 +21558,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.8.RELEASE</version> + <version>Edgware.SR4</version> </dependency> </dependencies> @@ -21609,7 +21609,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.8.RELEASE</version> + <version>Edgware.SR4</version> </dependency> </dependencies> @@ -21685,7 +21685,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=database diff --git a/Edgware.SR5/index.html b/Edgware.SR5/index.html index 7bcb249b..ebfe2a7d 100644 --- a/Edgware.SR5/index.html +++ b/Edgware.SR5/index.html @@ -90,7 +90,7 @@ $(addBlockSwitches);

-

1.3.8.RELEASE

+

Edgware.SR5

diff --git a/Edgware.SR5/multi/multi__client_side_usage_2.html b/Edgware.SR5/multi/multi__client_side_usage_2.html index 248424d8..52ad72f8 100644 --- a/Edgware.SR5/multi/multi__client_side_usage_2.html +++ b/Edgware.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.8.RELEASE</version> + <version>Edgware.SR5</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> diff --git a/Edgware.SR5/multi/multi__spring_cloud_config.html b/Edgware.SR5/multi/multi__spring_cloud_config.html index 2ea3f227..b7f83105 100644 --- a/Edgware.SR5/multi/multi__spring_cloud_config.html +++ b/Edgware.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.8.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 + Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

Edgware.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/Edgware.SR5/multi/multi__spring_cloud_consul.html b/Edgware.SR5/multi/multi__spring_cloud_consul.html index 2f67f582..78878285 100644 --- a/Edgware.SR5/multi/multi__spring_cloud_consul.html +++ b/Edgware.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.8.RELEASE

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.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/Edgware.SR5/multi/multi__spring_cloud_contract.html b/Edgware.SR5/multi/multi__spring_cloud_contract.html index 81ab7781..a689b6ac 100644 --- a/Edgware.SR5/multi/multi__spring_cloud_contract.html +++ b/Edgware.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, Jay Bryant

1.3.8.RELEASE

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.SR5

Prev   Next
79. Single Sign On Home 80. Spring Cloud Contract
\ No newline at end of file diff --git a/Edgware.SR5/multi/multi__spring_cloud_netflix.html b/Edgware.SR5/multi/multi__spring_cloud_netflix.html index 1041d3db..60260a88 100644 --- a/Edgware.SR5/multi/multi__spring_cloud_netflix.html +++ b/Edgware.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.8.RELEASE

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.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/Edgware.SR5/multi/multi__spring_cloud_sleuth.html b/Edgware.SR5/multi/multi__spring_cloud_sleuth.html index 81b43737..e67b3c1f 100644 --- a/Edgware.SR5/multi/multi__spring_cloud_sleuth.html +++ b/Edgware.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.8.RELEASE

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.SR5

Prev   Next
45. Broadcasting Your Own Events Home 46. Introduction
\ No newline at end of file diff --git a/Edgware.SR5/multi/multi_pr01.html b/Edgware.SR5/multi/multi_pr01.html index 826b67cb..61edc20b 100644 --- a/Edgware.SR5/multi/multi_pr01.html +++ b/Edgware.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.8.RELEASE

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

Version: Edgware.SR5

Prev   Next
Spring Cloud Home 1. Features
\ No newline at end of file diff --git a/Edgware.SR5/multi/multi_vault.config.backends.database-backends.html b/Edgware.SR5/multi/multi_vault.config.backends.database-backends.html index 86b4863e..77644fa8 100644 --- a/Edgware.SR5/multi/multi_vault.config.backends.database-backends.html +++ b/Edgware.SR5/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.8.RELEASE</version> + <version>Edgware.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/Edgware.SR5/multi/multi_vault.config.backends.html b/Edgware.SR5/multi/multi_vault.config.backends.html index 5d91ecab..c0140b30 100644 --- a/Edgware.SR5/multi/multi_vault.config.backends.html +++ b/Edgware.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.8.RELEASE</version> + <version>Edgware.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.8.RELEASE</version> + <version>Edgware.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.8.RELEASE</version> + <version>Edgware.SR5</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/Edgware.SR5/single/spring-cloud.html b/Edgware.SR5/single/spring-cloud.html index a10c6173..0acc969c 100644 --- a/Edgware.SR5/single/spring-cloud.html +++ b/Edgware.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.8.RELEASE

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.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 @@ -349,7 +349,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.8.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
+false.

Part II. Spring Cloud Config

Edgware.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
@@ -1263,7 +1263,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.8.RELEASE

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.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 @@ -4396,7 +4396,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.8.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 +packages to scan.

Part VII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer

Edgware.SR5

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 @@ -5254,7 +5254,7 @@ Just define a Reporter<Span> bean as presente } }; } -}

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.8.RELEASE

This project provides Consul integrations for Spring Boot apps through autoconfiguration +}

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.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 @@ -5738,7 +5738,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.8.RELEASE

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.SR5

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 @@ -11280,7 +11280,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.8.RELEASE</version> + <version>Edgware.SR5</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -11493,7 +11493,7 @@ dependency.

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


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

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


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

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


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) @@ -11556,7 +11556,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.8.RELEASE</version> + <version>Edgware.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/Edgware.SR5/spring-cloud.xml b/Edgware.SR5/spring-cloud.xml index 137b4de5..5da87bc7 100644 --- a/Edgware.SR5/spring-cloud.xml +++ b/Edgware.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.8.RELEASE +Version: Edgware.SR5 Features @@ -629,7 +629,7 @@ in downstream projects. You can also disable the creation of these beans by set Spring Cloud Config -1.3.8.RELEASE +Edgware.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. @@ -2152,7 +2152,7 @@ String name = "World"; Spring Cloud Netflix -1.3.8.RELEASE +Edgware.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 @@ -9128,7 +9128,7 @@ packages to scan. Spring Cloud Sleuth Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer -1.3.8.RELEASE +Edgware.SR5 Introduction @@ -10915,7 +10915,7 @@ class ReporterConfiguration { Spring Cloud Consul -1.3.8.RELEASE +Edgware.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 @@ -11990,7 +11990,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.8.RELEASE +Edgware.SR5 Spring Cloud Contract @@ -20751,7 +20751,7 @@ the test cases). Example Maven configuration: <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.3.8.RELEASE</version> + <version>Edgware.SR5</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -21323,7 +21323,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.3.8.RELEASE</version> + <version>Edgware.SR5</version> </dependency> </dependencies> @@ -21369,7 +21369,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.3.8.RELEASE</version> + <version>Edgware.SR5</version> </dependency> </dependencies> @@ -21420,7 +21420,7 @@ dependency. <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.3.8.RELEASE</version> + <version>Edgware.SR5</version> </dependency> </dependencies> @@ -21496,7 +21496,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=database