https://pact.io logo
Join Slack
Powered by
Hi all, Looking at the `contract_requiring_verific...
# pactflow
n
Hi all, Looking at the 
contract_requiring_verification_published
webhook event. Is there a reason this doesn’t fire when a new contract is published? (e.g. no previous contract between services)
👍 1
m
Good question! I’ll bring back to the team (a bunch on leave this week). And aim to get back to you next ewek
👍 2
n
Hey @Matt (pactflow.io / pact-js / pact-go) I forgot about this one. Is there an answer?
m
I’m sorry Nathan, I can’t recall now either.
@Beth (pactflow.io/Pact Broker/pact-ruby) is this expected behaviour?
b
@Nathan Deamer that's a good question. I have a vague memory of it being because there is no main branch configured for the provider, so it can't tell what branch to trigger the build for.
Yes - just double checked the code. The webhook expects to fill in a branch name and a version number. If there has been no version published by the provider, and it doesn't know what the main branch is of the provider, it can't fill in either of those things.
We could potentially use 
main
and 
HEAD
as stand in values in that situation.
n
@Beth (pactflow.io/Pact Broker/pact-ruby) Using 
main
and 
HEAD
sounds like it would work to me.
b
@Nathan Deamer the more I think about this, the less sure I am that this makes sense.
If there are no provider versions at all, that means the provider has not even got the provider-changed verifications running yet.
if they haven’t got the pacts verifying in their own build, it would seem strange that they would start with the pact changed workflow first.
What order did you set things up in?
Open in Slack
PreviousNext
Powered by