search

pactflow / roadmap

Public Pactflow issue tracker and roadmap
MIT License
15 stars 0 forks source link

PactV4 - Same provider name for BDCT & Message based interactions #102

Open jegadeesan-ponnusamy opened 1 year ago

jegadeesan-ponnusamy commented 1 year ago

Scenario: I have microservice which acts a provider (BDCT) with the pacticipant name "microservice-api". This same microservice will also acts as provider for message based interactions (2 event types - ServiceCreate & ServiceDelete). I planned to use the same pacticipant name "microservice-api" for message based interaction & BDCT. But unable to do so.

Issue: When I use the same pacticipant name "microservice-api", the message based interactions are automatically getting verified based on the OAS document published as part of BDCT. But I was expecting that the message based interactions shouldnt be verified against OAS contract and wait until I run the Provider verifier tests for "microservice-api" events.

Workaround: As per the discussion with the community support, we need this feature request for this item. For now, we can follow the work around of using 2 different provider names (one for BDCT & one for message based interactions). https://pact-foundation.slack.com/archives/CLS16AVEE/p1689695352765749?thread_ts=1688139376.146759&cid=CLS16AVEE

mefellows commented 1 year ago

Thanks for raising this @jegadeesan-ponnusamy.