Wondering if this is expected behavior or if we ar...
# pact-broker
l
Wondering if this is expected behavior or if we are doing something wrong. 1. Service A is deployed 2. Client B creates Pact via test 3. Client B goes through build pipeline a. pipeline calls verifier b. verifier creates matrix record for client B / service A c. verifier fails because service A gets pact but pact check fails 4. Client B build fails and does not deploy due to failing pact check 5. Service A is not deployable unless it satisfies the contract of client B even though it's not deployed If Client B had successfully deployed in the past so there is an older version of the contract in a verified state, then service A can still deploy even though it doesn't satisfy the new version. I'd expect this behavior even in the scenario above.
In case anyone sees this in the future, I believe this is the answer to my question. I'll report back definitively after we validate that. https://docs.pact.io/pact_broker/advanced_topics/pending_pacts
I looked at my co-workers repo and he is setting enable pending to true. So I'm back to wondering why this situation fails.
Ah...the issue that was created is likely why. He is setting a branch in the config.
b
@Lee Olsen this will be out soon. for the time being, set a tag as well
@Lee Olsen update to the latest version and let me know if you’re still having issues