Ondřej Hájek
02/06/2023, 10:53 AMcontract requiring verification published
which works nicely, except for one important scenario:
1. I make a pull request to my consumer, which changes the contract
2. My consumer pact tests pass and publish new pact to the broker
3. The provider verification job gets triggered, by the webhook
4. My can-i-deploy job correctly waits for the verification results and shows that I can’t deploy no sign
So far so good… but now I go to fix my provider according to the new contract and when I am done, the updated provider is merged, I want to go back to the PR for consumer and just restart the build and get Yesyes sign from can-I-deploy. This doesn’t work though, because the webhook is not triggered again. I understand, why it’s not triggered and I think I can solve it by using the contract published
event, but I don’t think that’s the best approach, is it? What am I missing? Thanks for any suggestions…Matt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)