Hi, I’ve got a question around the pact webhooks. ...
# pact-brokerj
James P
02/08/2023, 9:40 AMHi, I’ve got a question around the pact webhooks. Do they only get evaluated for use after a contract has been published? I was wondering what would happen in a scenario where for example there was a period of time where you were not publishing provider verification results and then started and implemented can i deploy, record deployments etc. If you ended rolling back to an older provider version, there might not be a contract verification so my question is, if a rollback doesn’t trigger a publish, is there no way to trigger a custom verification of the provider? Also, does can i deploy (consumer side) ever trigger a webhook? For background, we do not publish contracts post merging into trunk, we use can-i-deploy/record deployment from then on so curious what would happen in this scenario
m
Matt (pactflow.io / pact-js / pact-go)
02/08/2023, 10:17 AM
In that scenario, I believe the answer is no. The events are triggered based on a publication, so it wouldn’t know to trigger
Matt (pactflow.io / pact-js / pact-go)
02/08/2023, 10:18 AM
Is the concern that version A of the provider went to production, and then you started contract testing and version B of the provider was deployed which has passed all the contract testing checks.
Later on, you realised B needed to be rolled back, but
can-i-deployj
James P
02/08/2023, 10:28 AMCorrect
James P
02/08/2023, 10:31 AMI was hoping that maybe something would trigger an interaction at that point. I figured because you can configure a wait with can-i-deploy that it had the capability of triggering the interaction without a contract publish
m
Matt (pactflow.io / pact-js / pact-go)
02/08/2023, 11:40 AM
I don't think so. It feels a bit edge-casey. Is there a way you could just ensure the currently deployed version is also included in the initial pact rollout?
5 Views