Hello, I am a bit confused by this apparent issue...
# general
n
Hello, I am a bit confused by this apparent issue that i am encountering. Tbh I am not sure if it is an actual issue or if I am not doing things correctly. Anyway here is what is happening: I have a consumer that interacts with a provider using both HTTP and Kafka. I have two consumer tests for each, each creating its own pact file. I am publishing the Pact files to pactflow.io using the Pact cli tool (
pact-broker publish
), but when I go to the pactflow.io UI I can only see the HTTP interaction. However when I retrieve the latest pact for the provider I get a JSON file that contains both interactions and messages -- I used curl to retrieve the JSON. I also built a provider test but only for the HTTP interaction (using
HTTPVerifier
), what I am also seeing is that when I run the provider test it is attempting to verify the Kafka message. Has anyone experienced a similar situation?
Just a clarification the provider test is both verifying the HTTP interaction and the Message interaction. The message Message interaction obviously fails.
m
You need to have different names for providers of different types. That's resolved in the latest spec but I think you're using Go and we haven't added v4 support yet (it's quite new)
n
Indeed I am using Go. Thank you
That makes sense.
Any idea when v4 will be supported in GO?
m
Over the next few months it will gradually roll out, likely on a beta branch initially and then merged into mainline
n
Thank you 👍
👍 1