From a8de150b3479e26c0cc47f4d31b69f0ddacdd9aa Mon Sep 17 00:00:00 2001 From: Spencer Gibb Date: Wed, 12 Dec 2018 16:27:08 -0500 Subject: [PATCH] Updates version to Greenwich.RC1 --- Greenwich.RC1/index.html | 2 +- .../multi/multi__client_side_usage_2.html | 2 +- .../multi/multi__spring_cloud_config.html | 2 +- .../multi/multi__spring_cloud_consul.html | 2 +- .../multi/multi__spring_cloud_contract.html | 2 +- ..._spring_cloud_contract_verifier_setup.html | 2 +- .../multi/multi__spring_cloud_gateway.html | 2 +- .../multi/multi__spring_cloud_netflix.html | 2 +- .../multi/multi__spring_cloud_openfeign.html | 2 +- .../multi/multi__spring_cloud_sleuth.html | 2 +- Greenwich.RC1/multi/multi_pr01.html | 2 +- ...ult.config.backends.database-backends.html | 2 +- .../multi/multi_vault.config.backends.html | 6 ++-- Greenwich.RC1/single/spring-cloud.html | 28 ++++++++-------- Greenwich.RC1/spring-cloud.xml | 32 +++++++++---------- 15 files changed, 45 insertions(+), 45 deletions(-) diff --git a/Greenwich.RC1/index.html b/Greenwich.RC1/index.html index d7d9b070..412835ee 100644 --- a/Greenwich.RC1/index.html +++ b/Greenwich.RC1/index.html @@ -90,7 +90,7 @@ $(addBlockSwitches);
-

1.0.0.BUILD-SNAPSHOT

+

Greenwich.RC1

diff --git a/Greenwich.RC1/multi/multi__client_side_usage_2.html b/Greenwich.RC1/multi/multi__client_side_usage_2.html index 88d15089..e0f41b83 100644 --- a/Greenwich.RC1/multi/multi__client_side_usage_2.html +++ b/Greenwich.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.0.0.BUILD-SNAPSHOT</version> + <version>Greenwich.RC1</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> diff --git a/Greenwich.RC1/multi/multi__spring_cloud_config.html b/Greenwich.RC1/multi/multi__spring_cloud_config.html index 01cda6d3..41a33d76 100644 --- a/Greenwich.RC1/multi/multi__spring_cloud_config.html +++ b/Greenwich.RC1/multi/multi__spring_cloud_config.html @@ -1,6 +1,6 @@ - Part II. Spring Cloud Config
Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

1.0.0.BUILD-SNAPSHOT

Spring Cloud Config provides server-side 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. + Part II. Spring Cloud Config

Part II. Spring Cloud Config
Prev   Next

Part II. Spring Cloud Config

Greenwich.RC1

Spring Cloud Config provides server-side 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. diff --git a/Greenwich.RC1/multi/multi__spring_cloud_consul.html b/Greenwich.RC1/multi/multi__spring_cloud_consul.html index e5bea23c..ebf25ea6 100644 --- a/Greenwich.RC1/multi/multi__spring_cloud_consul.html +++ b/Greenwich.RC1/multi/multi__spring_cloud_consul.html @@ -1,6 +1,6 @@ - Part IX. Spring Cloud Consul

Part IX. Spring Cloud Consul
Prev   Next

Part IX. Spring Cloud Consul

1.0.0.BUILD-SNAPSHOT

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

Part IX. Spring Cloud Consul
Prev   Next

Part IX. Spring Cloud Consul

Greenwich.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/Greenwich.RC1/multi/multi__spring_cloud_contract.html b/Greenwich.RC1/multi/multi__spring_cloud_contract.html index d809814f..5d0dfba6 100644 --- a/Greenwich.RC1/multi/multi__spring_cloud_contract.html +++ b/Greenwich.RC1/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.0.0.BUILD-SNAPSHOT

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

Greenwich.RC1

Prev   Next
84. Single Sign On Home 85. Spring Cloud Contract
\ No newline at end of file diff --git a/Greenwich.RC1/multi/multi__spring_cloud_contract_verifier_setup.html b/Greenwich.RC1/multi/multi__spring_cloud_contract_verifier_setup.html index 8c663629..92da6635 100644 --- a/Greenwich.RC1/multi/multi__spring_cloud_contract_verifier_setup.html +++ b/Greenwich.RC1/multi/multi__spring_cloud_contract_verifier_setup.html @@ -383,7 +383,7 @@ the following options:

    groupid/artifactid where gropuid is slash separated.
  • contractsMode: Picks the mode in which stubs will be found and registered
  • deleteStubsAfterTest: If set to false will not remove any downloaded contracts from temporary directories
  • contractsRepositoryUrl: URL to a repo with the artifacts that have contracts. If it is not provided, use the current Maven ones.
  • contractsRepositoryUsername: The user name to be used to connect to the repo with contracts.
  • contractsRepositoryPassword: The password to be used to connect to the repo with contracts.
  • contractsRepositoryProxyHost: The proxy host to be used to connect to the repo with contracts.
  • contractsRepositoryProxyPort: The proxy port to be used to connect to the repo with contracts.

We cache only non-snapshot, explicitly provided versions (for example -+ or 1.0.0.BUILD-SNAPSHOT won’t get cached). By default, this feature is turned on.

88.2.8 Single Base Class for All Tests

When using Spring Cloud Contract Verifier in default MockMvc, you need to create a base ++ or Greenwich.RC1 won’t get cached). By default, this feature is turned on.

88.2.8 Single Base Class for All Tests

When using Spring Cloud Contract Verifier in default MockMvc, you need to create a base specification for all generated acceptance tests. In this class, you need to point to an endpoint, which should be verified.

package org.mycompany.tests
 
diff --git a/Greenwich.RC1/multi/multi__spring_cloud_gateway.html b/Greenwich.RC1/multi/multi__spring_cloud_gateway.html
index 33792b62..2f15227d 100644
--- a/Greenwich.RC1/multi/multi__spring_cloud_gateway.html
+++ b/Greenwich.RC1/multi/multi__spring_cloud_gateway.html
@@ -1,3 +1,3 @@
 
       
-   Part XV. Spring Cloud Gateway
Part XV. Spring Cloud Gateway
Prev   Next
Part XV. Spring Cloud Gateway
1.0.0.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
109. Lease lifecycle management (renewal and revocation) Home 110. How to Include Spring Cloud Gateway

\ No newline at end of file
+   Part XV. Spring Cloud Gateway
Part XV. Spring Cloud Gateway
Prev   Next
Part XV. Spring Cloud Gateway
Greenwich.RC1
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
109. Lease lifecycle management (renewal and revocation) Home 110. How to Include Spring Cloud Gateway

\ No newline at end of file
diff --git a/Greenwich.RC1/multi/multi__spring_cloud_netflix.html b/Greenwich.RC1/multi/multi__spring_cloud_netflix.html
index c7c77155..6981842a 100644
--- a/Greenwich.RC1/multi/multi__spring_cloud_netflix.html
+++ b/Greenwich.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.0.0.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
Greenwich.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/Greenwich.RC1/multi/multi__spring_cloud_openfeign.html b/Greenwich.RC1/multi/multi__spring_cloud_openfeign.html
index 0a4d04b7..b51516aa 100644
--- a/Greenwich.RC1/multi/multi__spring_cloud_openfeign.html
+++ b/Greenwich.RC1/multi/multi__spring_cloud_openfeign.html
@@ -1,4 +1,4 @@
 
       
-   Part IV. Spring Cloud OpenFeign
Part IV. Spring Cloud OpenFeign
Prev   Next
Part IV. Spring Cloud OpenFeign
1.0.0.BUILD-SNAPSHOT
This project provides OpenFeign integrations for Spring Boot apps through autoconfiguration
+   Part IV. Spring Cloud OpenFeign
Part IV. Spring Cloud OpenFeign
Prev   Next
Part IV. Spring Cloud OpenFeign
Greenwich.RC1
This project provides OpenFeign integrations for Spring Boot apps through autoconfiguration
 and binding to the Spring Environment and other Spring programming model idioms.
Prev   Next
21. HTTP Clients Home 22. Declarative REST Client: Feign

\ No newline at end of file
diff --git a/Greenwich.RC1/multi/multi__spring_cloud_sleuth.html b/Greenwich.RC1/multi/multi__spring_cloud_sleuth.html
index 9b2ac570..572a572c 100644
--- a/Greenwich.RC1/multi/multi__spring_cloud_sleuth.html
+++ b/Greenwich.RC1/multi/multi__spring_cloud_sleuth.html
@@ -1,3 +1,3 @@
 
       
-   Part VIII. Spring Cloud Sleuth
Part VIII. Spring Cloud Sleuth
Prev   Next
Part VIII. Spring Cloud Sleuth
Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer, Jay Bryant
1.0.0.BUILD-SNAPSHOT
Prev   Next
48. Broadcasting Your Own Events Home 49. Introduction

\ No newline at end of file
+   Part VIII. Spring Cloud Sleuth
Part VIII. Spring Cloud Sleuth
Prev   Next
Part VIII. Spring Cloud Sleuth
Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer, Jay Bryant
Greenwich.RC1
Prev   Next
48. Broadcasting Your Own Events Home 49. Introduction

\ No newline at end of file
diff --git a/Greenwich.RC1/multi/multi_pr01.html b/Greenwich.RC1/multi/multi_pr01.html
index 1fe10e8e..24cbdd20 100644
--- a/Greenwich.RC1/multi/multi_pr01.html
+++ b/Greenwich.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.0.0.BUILD-SNAPSHOT
Prev   Next
Spring Cloud Home 1. Features

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

\ No newline at end of file
diff --git a/Greenwich.RC1/multi/multi_vault.config.backends.database-backends.html b/Greenwich.RC1/multi/multi_vault.config.backends.database-backends.html
index 90de7657..ca9aecef 100644
--- a/Greenwich.RC1/multi/multi_vault.config.backends.database-backends.html
+++ b/Greenwich.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.0.0.BUILD-SNAPSHOT</version>
+        <version>Greenwich.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/Greenwich.RC1/multi/multi_vault.config.backends.html b/Greenwich.RC1/multi/multi_vault.config.backends.html index acf63c22..1b3fe101 100644 --- a/Greenwich.RC1/multi/multi_vault.config.backends.html +++ b/Greenwich.RC1/multi/multi_vault.config.backends.html @@ -46,7 +46,7 @@ dependency.

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


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

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


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

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


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/Greenwich.RC1/single/spring-cloud.html b/Greenwich.RC1/single/spring-cloud.html index c2969b7e..05a9b54d 100644 --- a/Greenwich.RC1/single/spring-cloud.html +++ b/Greenwich.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.0.0.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: Greenwich.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 Applications, 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. @@ -357,7 +357,7 @@ You can find the latest Spring Boot versions here [https://spring.io/projects/sp If you want to learn more about the Spring Cloud Release train compatibility, you can visit this page [https://spring.io/projects/spring-cloud#overview] and check the [Release Trains] section.

In order to disable this feature, set spring.cloud.compatibility-verifier.enabled to false. If you want to override the compatible Spring Boot versions, just set the spring.cloud.compatibility-verifier.compatible-boot-versions property with a comma separated list -of compatible Spring Boot versions.

Part II. Spring Cloud Config

1.0.0.BUILD-SNAPSHOT

Spring Cloud Config provides server-side 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. +of compatible Spring Boot versions.

Part II. Spring Cloud Config

Greenwich.RC1

Spring Cloud Config provides server-side 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. @@ -1015,7 +1015,7 @@ in bootstrap.yml, as shown in the following example token: YourVaultToken

10.9 Nested Keys In Vault

Vault supports the ability to nest keys in a value stored in Vault, as shown in the following example:

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

This command writes a JSON object to your Vault. To access these values in Spring, you would use the traditional dot(.) annotation, as shown in the following example

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

The preceding code would sets the value of the name variable to appAsecret.

Part III. Spring Cloud Netflix

1.0.0.BUILD-SNAPSHOT

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

The preceding code would sets the value of the name variable to appAsecret.

Part III. Spring Cloud Netflix

Greenwich.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 @@ -2120,7 +2120,7 @@ You can also disable retry functionality on a route-by-route basis by setting ClosableHttpClient if you are using the Apache Http Cient or OkHttpClient if you are using OK HTTP.

[Note]Note

When you create your own HTTP client, you are also responsible for implementing the correct connection management strategies for these clients. -Doing so improperly can result in resource management issues.

Part IV. Spring Cloud OpenFeign

1.0.0.BUILD-SNAPSHOT

This project provides OpenFeign integrations for Spring Boot apps through autoconfiguration +Doing so improperly can result in resource management issues.

Part IV. Spring Cloud OpenFeign

Greenwich.RC1

This project provides OpenFeign integrations for Spring Boot apps through autoconfiguration and binding to the Spring Environment and other Spring programming model idioms.

22. Declarative REST Client: Feign

Feign is a declarative web service client. It makes writing web service clients easier. To use Feign create an interface and annotate it. It has pluggable annotation support including Feign annotations and JAX-RS annotations. Feign also supports pluggable encoders and decoders. Spring Cloud adds support for Spring MVC annotations and for using the same HttpMessageConverters used by default in Spring Web. Spring Cloud integrates Ribbon and Eureka to provide a load balanced http client when using Feign.

22.1 How to Include Feign

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

Example spring boot app

@SpringBootApplication
@@ -4505,7 +4505,7 @@ following example:
@RemoteApplicationEventScan are equivalent, in that the
 com.acme package is registered by explicitly specifying the packages on
-@RemoteApplicationEventScan.
[Note]Note
You can specify multiple base packages to scan.

Part VIII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer, Jay Bryant

1.0.0.BUILD-SNAPSHOT

49. Introduction

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

49.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. +@RemoteApplicationEventScan.

[Note]Note

You can specify multiple base packages to scan.

Part VIII. Spring Cloud Sleuth

Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer, Jay Bryant

Greenwich.RC1

49. Introduction

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

49.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. Spans 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 IDs (normally IP addresses).

Spans can be started and stopped, and they keep track of their timing information. Once you create a span, you must stop it at some point in the future.

[Tip]Tip

The initial span that starts a trace is called a root span. The value of the ID @@ -5468,7 +5468,7 @@ To disable Zuul support, set the spring.sleuth.zuul.enable Check them out at the following links:

Part IX. Spring Cloud Consul

1.0.0.BUILD-SNAPSHOT

This project provides Consul integrations for Spring Boot apps through autoconfiguration +and order some beers. Then check Zipkin for traces.

Part IX. Spring Cloud Consul

Greenwich.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 @@ -6110,7 +6110,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 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.0.0.BUILD-SNAPSHOT

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

Greenwich.RC1

85. 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 @@ -7894,7 +7894,7 @@ the following options:

    groupid/artifactid where gropuid is slash separated.
  • contractsMode: Picks the mode in which stubs will be found and registered
  • deleteStubsAfterTest: If set to false will not remove any downloaded contracts from temporary directories
  • contractsRepositoryUrl: URL to a repo with the artifacts that have contracts. If it is not provided, use the current Maven ones.
  • contractsRepositoryUsername: The user name to be used to connect to the repo with contracts.
  • contractsRepositoryPassword: The password to be used to connect to the repo with contracts.
  • contractsRepositoryProxyHost: The proxy host to be used to connect to the repo with contracts.
  • contractsRepositoryProxyPort: The proxy port to be used to connect to the repo with contracts.

We cache only non-snapshot, explicitly provided versions (for example -+ or 1.0.0.BUILD-SNAPSHOT won’t get cached). By default, this feature is turned on.

88.2.8 Single Base Class for All Tests

When using Spring Cloud Contract Verifier in default MockMvc, you need to create a base ++ or Greenwich.RC1 won’t get cached). By default, this feature is turned on.

88.2.8 Single Base Class for All Tests

When using Spring Cloud Contract Verifier in default MockMvc, you need to create a base specification for all generated acceptance tests. In this class, you need to point to an endpoint, which should be verified.

package org.mycompany.tests
 
@@ -12638,7 +12638,7 @@ the test cases). Example Maven configuration:
<dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-starter-vault-config</artifactId>
-        <version>1.0.0.BUILD-SNAPSHOT</version>
+        <version>Greenwich.RC1</version>
     </dependency>
     <dependency>
         <groupId>org.springframework.boot</groupId>
@@ -12930,7 +12930,7 @@ dependency.
<dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-vault-config-consul</artifactId>
-        <version>1.0.0.BUILD-SNAPSHOT</version>
+        <version>Greenwich.RC1</version>
     </dependency>
 </dependencies>

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

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


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

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


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) @@ -12993,7 +12993,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.0.0.BUILD-SNAPSHOT</version> + <version>Greenwich.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 @@ -13143,7 +13143,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 XV. Spring Cloud Gateway

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

110. 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 XV. Spring Cloud Gateway

Greenwich.RC1

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.

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

[Important]Important

Spring Cloud Gateway requires the Netty runtime provided by Spring Boot and Spring Webflux. It does not work in a traditional Servlet Container or built as a WAR.

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

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

[Note]Note

URIs defined in routes without a port will get a default port set to 80 and 443 for HTTP and HTTPS URIs respectively.

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

113.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/Greenwich.RC1/spring-cloud.xml b/Greenwich.RC1/spring-cloud.xml
index 94452ac6..48468fb6 100644
--- a/Greenwich.RC1/spring-cloud.xml
+++ b/Greenwich.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.0.0.BUILD-SNAPSHOT
+Version: Greenwich.RC1
 
 
 Features
@@ -699,7 +699,7 @@ of compatible Spring Boot versions.
 
 Spring Cloud Config
 
-1.0.0.BUILD-SNAPSHOT
+Greenwich.RC1
 Spring Cloud Config provides server-side 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.
@@ -2088,7 +2088,7 @@ String name = "World";
 
 Spring Cloud Netflix
 
-1.0.0.BUILD-SNAPSHOT
+Greenwich.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
@@ -4204,7 +4204,7 @@ Doing so improperly can result in resource management issues.
 
 Spring Cloud OpenFeign
 
-1.0.0.BUILD-SNAPSHOT
+Greenwich.RC1
 This project provides OpenFeign integrations for Spring Boot apps through autoconfiguration
 and binding to the Spring Environment and other Spring programming model idioms.
 
@@ -10242,7 +10242,7 @@ public class BusConfiguration {
 Spring Cloud Sleuth
 
 Adrian Cole, Spencer Gibb, Marcin Grzejszczak, Dave Syer, Jay Bryant
-1.0.0.BUILD-SNAPSHOT
+Greenwich.RC1
 
 
 Introduction
@@ -12316,7 +12316,7 @@ and order some beers. Then check Zipkin for traces.
 
 Spring Cloud Consul
 
-1.0.0.BUILD-SNAPSHOT
+Greenwich.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
@@ -13607,7 +13607,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.0.0.BUILD-SNAPSHOT
+Greenwich.RC1
 
 
 Spring Cloud Contract
@@ -14064,7 +14064,7 @@ setup or messaging test setup).
 application and the stub artifacts are built and installed in the local Maven repository.
 Information about installing the stubs jar to the local repository appears in the logs, as
 shown in the following example:
-[INFO] --- spring-cloud-contract-maven-plugin:1.0.0.BUILD-SNAPSHOT:generateStubs (default-generateStubs) @ http-server ---
+[INFO] --- spring-cloud-contract-maven-plugin:Greenwich.RC1:generateStubs (default-generateStubs) @ http-server ---
 [INFO] Building jar: /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar
 [INFO]
 [INFO] --- maven-jar-plugin:2.6:jar (default-jar) @ http-server ---
@@ -14696,7 +14696,7 @@ stubs. You need to skip the test generation and execution. When you execute:$ cd local-http-server-repo
 $ ./mvnw clean install -DskipTests
 In the logs, you see something like this:
-[INFO] --- spring-cloud-contract-maven-plugin:1.0.0.BUILD-SNAPSHOT:generateStubs (default-generateStubs) @ http-server ---
+[INFO] --- spring-cloud-contract-maven-plugin:Greenwich.RC1:generateStubs (default-generateStubs) @ http-server ---
 [INFO] Building jar: /some/path/http-server/target/http-server-0.0.1-SNAPSHOT-stubs.jar
 [INFO]
 [INFO] --- maven-jar-plugin:2.6:jar (default-jar) @ http-server ---
@@ -16672,7 +16672,7 @@ use the current Maven ones.
 
 
 We cache only non-snapshot, explicitly provided versions (for example
-+ or 1.0.0.BUILD-SNAPSHOT won’t get cached). By default, this feature is turned on.
++ or Greenwich.RC1 won’t get cached). By default, this feature is turned on.
 
 

 Single Base Class for All Tests
@@ -23925,7 +23925,7 @@ the test cases). Example Maven configuration:
     <dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-starter-vault-config</artifactId>
-        <version>1.0.0.BUILD-SNAPSHOT</version>
+        <version>Greenwich.RC1</version>
     </dependency>
     <dependency>
         <groupId>org.springframework.boot</groupId>
@@ -24901,7 +24901,7 @@ dependency.
     <dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-vault-config-consul</artifactId>
-        <version>1.0.0.BUILD-SNAPSHOT</version>
+        <version>Greenwich.RC1</version>
     </dependency>
 </dependencies>
 
@@ -24947,7 +24947,7 @@ dependency.
     <dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-vault-config-rabbitmq</artifactId>
-        <version>1.0.0.BUILD-SNAPSHOT</version>
+        <version>Greenwich.RC1</version>
     </dependency>
 </dependencies>
 
@@ -24998,7 +24998,7 @@ dependency.
     <dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-vault-config-aws</artifactId>
-        <version>1.0.0.BUILD-SNAPSHOT</version>
+        <version>Greenwich.RC1</version>
     </dependency>
 </dependencies>
 
@@ -25077,7 +25077,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=database
 
@@ -25438,7 +25438,7 @@ after application shutdown.
 
 Spring Cloud Gateway
 
-1.0.0.BUILD-SNAPSHOT
+Greenwich.RC1
 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.