Feat/v2

[YOU54F]

We would like to implement Pact V3 & V4 Specification support for Pact Ruby enabled via the rust core

Pact Ruby V2

Fixes #317, #318, #319

Documentation

https://github.com/pact-foundation/pact-ruby/blob/feat/v2/documentation/README_V2.md

Delivered Features

• Multiple specification support 1️⃣ 2️⃣ 3️⃣ 4️⃣
• Multiple interaction types (consumer / provider )
  • ✅ Synchronous/HTTP
  • ✅ Asynchronous/Message
  • ✅ Synchronous/Message
• Pact Plugin support
  • ✅ gRPC (Consumer / Provider)
  • ✅ Generic Http (Consumer side)
  • ✅ Generic Asynchronous/Message (Consumer side)
  • ✅ Generic Synchronous/Message (Consumer side)
  • 🚧 Generic (Provider side)
• Matchers
  • See docs
• Generators
  • See docs

Validation

The following projects were designed for pact-ruby-v1 and have been migrated to pact-ruby-v2. They can serve as an example of the work required.

• pact broker client
  • v2 Feat/v2 pact_broker-client#198
• pact broker
  • v2 chore(test): use pact-ruby v2 (rust core) along ruby-core, for verifications pact_broker#843
• animal service
  • v1
    • In repo: example/animal-service
    • Standalone: https://github.com/safdotdev/animal-service/tree/feat/v1
  • v2
    • In repo: example/animal-service-v2
    • Standalone: https://github.com/safdotdev/animal-service/tree/feat/v2
• zoo app
  • v1
    • In repo: example/zoo-app
    • Standalone: https://github.com/safdotdev/zoo-app/tree/feat/v1
  • v2
    • In repo: example/zoo-app-v2
    • Standalone: https://github.com/safdotdev/zoo-app/tree/feat/v2
• message consumer/provider
  • v1 chore: update to support latest rubies and add test safdotdev/pact-ruby-demo#2
  • v2 Feat/v2 safdotdev/pact-ruby-demo#3
• e2e http consumer/provider
  • v1
  • v2 Feat/pact ruby v2 safdotdev/pact-ruby-e2e-example#1

V3 Related Issues

Will be tagging and closing related v3/v4 issues, and linking to this meta issue

• Pact v3 specification implementation for Pact Ruby #266
• Change "headers" to "header" in v3 matching rules pact-support#67
• Invalid path value for HTTP header matcher. pact-standalone#34
• Ignoring unsupported matching rules on arrays pact-support#61
• Matching rules input / output mismatch pact-support#65
• PactSpec v3 not supported? pact-provider-verifier#61
• Support v3 in pact-ruby-standalone pact-standalone#143
• URL based matching #107
• Writing pact file results in non spec v3 compatible matching rules #157
• Documentation mismatch on what is expected by the provider state setup url endpoint pact-provider-verifier#19
• Message Provider - Provide access to, and validate message metadata pact-message-ruby#6
• Correctly encode message body using v3 spec pact-message-ruby#5
• Add support for v3 multiple provider states  pact-message-ruby#4
• Add support for the new v3 matching rules format pact-message-ruby#2
• Issue with interaction providerState and set_up_provider_states #192
• Support params in provider_state (v3) #168
• Pact V3 Tracking Issue #318

V4 Related Issues

Will be tagging and closing related v3/v4 issues, and linking to this meta issue

• Pact v4 specification implementation for Pact Ruby #267

[YOU54F]

This is published as a test gem to

https://rubygems.org/gems/pact-v2

there are two versions. the first contains only the v1 deps, the second contains both v1 & v2 deps.

It doesn’t seem rubygems supports conditional gems ( i wanted to control it by env var ) i did look at a ruby extension to install additional gems but these wouldn’t be known to bundler

the test gem will ultimately be deleted, so please don’t rely in production. ty

[YOU54F]

Lets go!

For anyone who comes across this, if I have inadvertently broken your workflow, you may want to pin to the release prior to this going out

https://github.com/pact-foundation/pact-ruby/releases/tag/v1.66.2

it has been designed to work side by side, so the only blocker for people I imagine, will be the new set of dependencies.

In version 2, the old pact-ruby v1 interface will be removed, and the v2 namespaced code will be moved to the root