With this functionality you can have one centralized repository containing all contracts. This repo will have to produce a JAR containing all contracts. The layout of the repository can be arbitrary but some sensible defaults are assumed. The producer will be able to then download that JAR and produce tests and stubs from it.
fixes#38
* reorganized the entries (now the Contract details went to the very bottom)
* added FAQ section where versioning and dynamic props are better defined
* added in a couple of places links to Groovy JSON docs
fixes#69
before this change the support for Stub Runner Boot with Service Discovery was pretty useless since Stub Runner stubbed service discovery. That makes a lot of sense in unit / integration tests but not when you want to do some version of end to end tests.
With this change you can pass a property to enable automated registration of stubs in Service Discovery.
Technical changes:
* Added Zookeeper registration
* Added Eureka registration
* Added Consul registration
* Added checkstyle plugin - fixed part of exceptions
there was a problem with the way property related to array size check was passed. Not only was the condition inverse, but also the properties weren't passed.
With this change those issues were fixed, we've added the missing maven plugin feature and ensured that the array check is the default option.
fixes#60
There is no need for users to know about any special contract-specific
Message object (payload and headers). Once you see that, it seems like
there is no need for it internally either. So this change removes the
message wrapper type and cleans up the interfaces it touches.
with this change if in the DSL the regex is not in the valid place - an exception will be thrown
if the regex is passed properly but there is no other value (client / server) - it will get generated
fixes#32
to org.springframework.cloud from org.springframework.cloud.contract
also stopped running an http server if the contract doesn't support it
added back stub runner modules
