Hi, I think it is a bug but I am not sure. I cre...
# pactflow
r
Hi, I think it is a bug but I am not sure. I create a webhook with Consumer = All consumers and Provider = Service1 When I then click on Test Webhook however I get send what looks like all possible combination, completely spamming my github action which is only for ONE provider... I would have expected that they send all configurations for the configured webhook instead, so all consumer-provider pairs that include my chosen provider Is that an intended process? If so I need to update our documentation with a warning to not use that button 😅
m
Can you please elaborate on what github actions spawned? Multiple builds for the one provider? I suspect if you select “ALL” consumers, it will create a webhook for each consumer for that provider
r
so I have a webhook saying :all consumers, provider = Service1 I have a github API call that triggers the repository workflow of that particular provider. What I see when I click test is that I get ALL provider/consumer combinations leading to hundreds of github workflow calls. So eg. ServiceB -> Service D (Service one is not part of that pair) Service 1 -> Service 2 (Service is here consumer and not the provider) luckily with a reload you seem to be able to stop the spamming, as I could not find a stop button 😅
oh and in addition I now reproduced that webhook call locally so I do not need that button anymore, becauase for us with so many consumers/providers this button is unfortunately unusable
just to give a number, I started working on the workflow about half an hour ago and I already have 1700 workflow calls 🙈
m
wow, that’s….a bit crazy
The logic for a webhook “test” belongs in the open source pact broker, somewhere in here: https://github.com/pact-foundation/pact_broker/blob/master/lib/pact_broker/webhooks/trigger_service.rb
r
ah interesting I thought that is something pactflow specific. I will raise a bug ticket there then, thanks 🙂
👍 1
@Matt (pactflow.io / pact-js / pact-go) Here the pact broker side seems to not be able to reproduce the issue and say one possibility is that it is a bug in the pactflow layer after all. Could you please have a look?
m
Thanks Ruth, yes we’ve tracked this internally. Yousaf works for us so we’ve added it to our backlog for review
r
super thank you