pact-provider-verifier 1.19.0 → 1.20.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4816191834c42acad2eb1b2d1c23ad3080946f7d38304cccd2773aba2fc224c8
-  data.tar.gz: aa706e5dcf1069847773c7d547ee8d19d0f22020ccea133c77861052e33bf63c
+  metadata.gz: f4d877e456eddfe42cc7b33ca0bd242cc9d25f15a859ba799b72be0383a24064
+  data.tar.gz: b96350334233dd8fc1164c18482890ce7e0644a3c462c91350dcdabafd3b4047
 SHA512:
-  metadata.gz: 800639f786836a31e616b9455fdf2b046d244345a1ad0f81e0de416ad59238afebf794f8bc05bab11ad625dbe1b8e8da696b12d5ebeca307cd36c34fb0241e67
-  data.tar.gz: 2291ff8495f596a5bb15eded82328fabddf58065a6626881efbbe44c8de264ca35ba30628375410ce283bac88e38166b5485917946267090202885cf2e17183d
+  metadata.gz: f70528ae38442f641089226d03ec100802e3f9f77adabcefb2687e017f2405c4c745d105c6e8d82db5d741c4071a7980a42a24b7eea05e855254c71e6dcbb811
+  data.tar.gz: 6af6026d002d9a0c10ad63906a13828bbcf6fe70c3d94b21a163a453a7d05aea02ff37ea1b2c4f7f08dd114ddc5a3dcfb42bbb015b22893f88d4cf68a735dd9d

data/CHANGELOG.md

@@ -1,3 +1,13 @@
+<a name="v1.20.0-1"></a>
+### v1.20.0-1 (2018-10-04)
+
+
+#### Features
+
+* **pact specification v3**
+  * add support for multiple provider states and params	 ([556b957](/../../commit/556b957))
+
+
 <a name="v1.18.0-1"></a>
 ### v1.18.0-1 (2018-09-11)
 

data/Gemfile

@@ -4,6 +4,6 @@ gemspec
 
 if ENV['X_PACT_DEVELOPMENT']
   gem "pact", path: '../pact'
-  gem "pact-message", path: '../pact-message'
+  gem "pact-message", path: '../pact-message-ruby'
   gem "pact-support", path: '../pact-support'
 end

data/README.md

@@ -127,7 +127,11 @@ Rather than tearing down the specific test data created after each interaction,
 
 Note that the HTTP endpoint does not have to actually be within your application - it just has to have access to the same data store. So if you cannot add "test only" endpoints during your verification, consider making a separate app which shares credentials to your app's datastore. It is highly recommended that you run your verifications against a locally running provider, rather than a deployed one, as this will make it much easier to stub any downstream calls, debug issues, and it will make your tests run as fast as possible.
 
-Ignore the `states` array that you will see if you happen to print out the live provider state set up request body - that was an attempt to make the set up call forwards compatible with the v3 pact specification, which allows multiple provider states. Unfortunately, this forwards compatibilty attempt failed, because the v3 provider states support a map of params, not just a name, so it should have been `{ "state": { "name": "PROVIDER_STATE, "params": {...} } }`.
+Ignore the `states` array that you will see if you happen to print out the live provider state set up request body - that was an attempt to make the set up call forwards compatible with the v3 pact specification, which allows multiple provider states. Unfortunately, this forwards compatibilty attempt failed, because the v3 provider states support a map of params, not just a name, so it should have been `{ "state": { "name": "PROVIDER_STATE, "params": {...} } }`. See the next section for the actual v3 support.
+
+#### Pact specification v3 provider state support
+
+The v3 Pact specification adds support for multiple provider states, and provider state params. If you are verifying a pact with multiple provider states, then set up URL will be invoked once for each state. The `params` hash from the pact will also be passed through in the JSON document with the key name `params`.
 
 ### Using the Pact Broker with Basic authentication
 

data/lib/pact/provider_verifier/set_up_provider_state.rb

@@ -11,6 +11,7 @@ module Pact
         @provider_state = provider_state
         @consumer = consumer
         @options = options
+        @params = (options && options[:params]) || {}
       end
 
       def self.call provider_state, consumer, options
@@ -30,7 +31,7 @@ module Pact
 
       private
 
-      attr_reader :provider_state, :consumer
+      attr_reader :provider_state, :consumer, :params
 
       def post_to_provider_state
         verbose = verbose?
@@ -59,7 +60,12 @@ module Pact
         connection.post do |req|
           req.headers["Content-Type"] = "application/json"
           add_custom_provider_header req
-          req.body = {consumer: consumer, state: provider_state, states: [provider_state] }.to_json
+          req.body = {
+            consumer: consumer,
+            state: provider_state,
+            states: [provider_state],
+            params: params
+          }.to_json
         end
       end
 

data/lib/pact/provider_verifier/version.rb

@@ -1,5 +1,5 @@
 module Pact
   module ProviderVerifier
-    VERSION = "1.19.0"
+    VERSION = "1.20.0"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pact-provider-verifier
 version: !ruby/object:Gem::Version
-  version: 1.19.0
+  version: 1.20.0
 platform: ruby
 authors:
 - Matt Fellows
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-09-18 00:00:00.000000000 Z
+date: 2018-10-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -31,34 +31,28 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.34'
+        version: '1.36'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.34'
+        version: '1.36'
 - !ruby/object:Gem::Dependency
   name: pact-message
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.4'
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 0.4.1
+        version: '0.5'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.4'
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 0.4.1
+        version: '0.5'
 - !ruby/object:Gem::Dependency
   name: faraday
   requirement: !ruby/object:Gem::Requirement