From 6991dc6dc32b86afdb8aff4245abcfeb85b05d74 Mon Sep 17 00:00:00 2001
From: Marcin Grzejszczak
You can pass those values also via properties from your deployment pipeline.
-Another way of storing contracts other than having them with the producer is keeping them in a common place.
It can be related to security issues where the consumers can’t clone the producer’s code. Also if you keep
@@ -2256,17 +2266,15 @@ Those poms are necessary for the consumer side to run mvn clean install -D
</assembly>
Workflow
-The workflow would look similar to the one presented in the Step by step guide to CDC. The only difference
is that the producer doesn’t own the contracts anymore. So the consumer and the producer have to work on
common contracts in a common repository.
Consumer
-When the consumer wants to work on the contracts offline, instead of cloning the producer code, the
consumer team clones the common repository, goes to the required producer’s folder (e.g. com/example/server)
@@ -2284,9 +2292,9 @@ You need to have Maven installed
Producer
As a producer it’s enough to alter the Spring Cloud Contract Verifier to provide the URL and the dependency of the JAR containing the contracts:
@@ -2319,6 +2327,7 @@ when some incompatible changes are done.