Pact Foundation

The two interactions above are real pact generated by consumer test. Check out the `_id` and `key` values which are different.

Its written in golang following similar pattern here: <https://github.com/pact-foundation/pact-go/blob/2.x.x/examples/grpc/grpc_consumer_test.go>

Also am not sure if these two fields can cause pact content to be changed causing webhook to be triggered 

`_id` is generated by the Pact broker, I think it may just be a random key, but it could maybe be generated on the contents.

`key` is a unique key for the interaction, and will be generated from the contents of the interaction if not provided.

Because `key` is changing, it means your interaction contents are different.

Interesting as i compared the two pacts which are identical but yet pact broker thinks they are different 

The only difference i see is the 'key' and '_id' 

It might be <https://github.com/pact-foundation/pact-go/issues/230>

I suspect the `_id` changing is not relevant to the problem, but the `key` would definitely trigger a “change”

yeah looks like it, we never set this value for rest or kafka interactions where it works fine 

FYI updated the issue above - looks like I’ve reproduced it in Go

Now to see if I can do the same in the core