Hi Pact team 🙂 We have recently integrated our CI/CD flows with Pact, and we are seeing a behaviour that is being challenging to explain 😅 What we see is that the webhook (

contract_content_changed

event) gets executed way too many times from what we would expect. I was trying to debug what is going on looking at this, and what we see is that this is the message that I see constantly:

"Scheduling job for webhook with uuid ap7c1tk-AdEYyphWBVieIg"

. But it looks like the contract should have not changed, so I'm clearly missing something. Is there any way to actually see what are the 2 versions of the contract the Broker is comparing to understand what is going on? Also, as far as I've seen in the documentation, this could also explain what is happening:

If the relevant consumer version has any tags, then for each tag, check if the content is different from the previous latest version for that tag. It is 'changed' if any of the checks are true. One side effect of this is that brand new tags will trigger a pact changed event, even if the content is the same as a previous version.

But all the versions published are tagging with

master

, so I'm not sure if there is anything else I should be looking at...

There is a diff endpoint on the broker you can use to check what has changed

Thank you Timothy! Could you help me find that endpoint? Can I get there using the HAL Browser? Or can I find it somewhere in the documentation?e

If you navigate to the pact in the HAL browser, there should be a relation to discover previous versions of the integration

I think I have seen it now, but is there a way to get that content in a "plain json" format? What I'm getting is the Pact itself but visualized using the Pact Broker browser, which is good, but not very diff-friendly 😅

ohhh, now I see that 🤘 🤘 🤘 🤘 🤘

You're welcome. If it helps, I didn't actually find what I was looking for either.

@Rubén Pérez you should be seeing output during the publishing step that tells you why the webhook has been triggered.

Thank you Beth 🙂 I saw in the logs that the webhook was triggered, but I didn't see why. I saw one of the options in the logs:

Scheduling job for webhook with uuid ap7c1tk-AdEYyphWBVieIg

Which looks like just a "contract change" to me. But the consumer team told me that they didn't change anything for some time, but still the provider tests got triggered between 10 and 20 times per day. I just needed some help to try to see how the contract was actually changing... And you all helped me. For the record, I was able to see the changes and understand what was happening. In this case, the consumer tests were using

form-data

, which uses a

boundary

field internally. That field was created randomly for every test execution, and that was the "change" introduced in every single CI consumer build.

And you all helped me. For the record, I was able to see the changes and understand what was happening. In this case, the consumer tests were using

form-data

, which uses a

boundary

field internally. That field was created randomly for every test execution, and that was the “change” introduced in every single CI consumer build.

good pickup! That’ll do it

also, you would be better to use the new webhook “contract requiring verification published”

I know, but I have not been able to get into it yet 😅