Feature Requests

Allow pact to be extended by a general purpose plugin infrastructure See https://github.com/pact-foundation/pact-specification/issues/83 for proposal

Metadata injection support is currently available in Java, for example ' https://github.com/pact-foundation/pact-plugins/blob/main/examples/gRPC/metadata/provider-jvm/server/src/test/java/io/pact/example/grpc/provider/PactVerificationTest.java#L60 ' . This function is needed in cases such as providing an authentication token to be able to verify the contract file using "verifyProvider" if the producer service is performing token authorization.

Kafka is emerging as a standard for sharing business events across the Enterprise. First class connectors for Kafka, and also integration/consideration for the Avro schema registry would simplify adoption.

Creation of a GraphQL plugin that is aware of the syntax and semantics of a GraphQL client call (the provider response is standard JSON over HTTP). Whilst GraphQL is currently supported by Pact (see https://pactflow.io/blog/contract-testing-a-graphql-api/ ) users need to be aware of the HTTP abstractions and JSON payload of GraphQL, and to handle the query either: a) ensure the consumer payload matches exactly character-for-character what was expected, or b) use an ugly regex to allow additional spaces/characters in the query

Apache Avro is a common data interchange format. Supporting it enables use cases for data pipelines and event driven architectures with tools like Kafka.

Websockets is a popular transport for real-time and bi-directional communication between clients and servers.

Creation of a Transport plugin to support AMQP. The Advanced Message Queueing Protocol (AMQP) is an open standard application layer protocol for message-oriented middleware.

The SSE protocol has a slightly peculiar format and can't be easily tested with Pact today - whilst the protocol is text based, Pact doesn't understand the various tokens and therefore payloads would currently require exact matching, which is rather brittle. SSE could be developed as a Content Matcher plugin and optionally a transport (the Asynchronous message type could easily model this interaction without a transport if needed) https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events#event_stream_format

Create an idiomatic SOAP interface as a Plugin. Whilst you can do XML matching in several languages, not all support it, and furthermore there is boilerplate in places - such as SOAP envelope, security, headers etc.

Creation of a JMS Transport and Content Matcher plugin.