Matt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
Paul Beigang
02/05/2025, 12:26 PMTim Vahlbrock
02/06/2025, 10:07 AMcontract_requiring_verification_published
event when no provider has ever verified a contract from this consumer? So if I want to trigger the pipeline for a brand new interface I also need to add the contract_content_changed
event to the webhook configuration?Matt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
Tim Vahlbrock
02/06/2025, 10:47 AMTim Vahlbrock
02/06/2025, 10:48 AMTim Vahlbrock
02/06/2025, 11:06 AMGabriel Vasconcelos
02/07/2025, 11:01 AMPiyush Sardana
02/08/2025, 10:35 AMSpencer
02/11/2025, 3:34 PMGitHub
02/13/2025, 12:30 PMGitHub
03/04/2025, 1:21 PMGitHub
03/06/2025, 5:06 PMGitHub
03/06/2025, 7:01 PMChris
03/11/2025, 6:11 AMpact-broker record-release
?
Also, how do we bulk record-support-ended
them?Ksawery Karwacki
03/17/2025, 5:48 PMGustavo Souza
04/03/2025, 6:16 PMJun Yi
04/10/2025, 3:03 AMstaging
and production
, which may contain different code as features are tested in staging before being rolled out to production.
1. Would it make sense to maintain separate sets of Pact stages for each branch?
2. I've observed that when a webhook is triggered, the verification always runs against the main branch (staging), regardless of which branch initiated the process. This could potentially cause issues when the branches diverge.
Any suggestions on how we can improve this setup or handle branch-specific verification more effectively?
Thanks!Matt (pactflow.io / pact-js / pact-go)
Would it make sense to maintain separate sets of Pact stages for each branch?I’m not sure I entirely follow. The concept of “branches” are there to map changes for a given branch. Are you using
pact-broker record-deployment
when you deploy to each environment?
I’ve observed that when a webhook is triggered, the verification always runs against the main branch (staging), regardless of which branch initiated the process. This could potentially cause issues when the branches diverge.When a webhook fires, it specifies in the payload which version (and branch/environment) that it needs to check against. Your webhook target should read the value of that body, and checkout the correct code accordingly. See also https://docs.pact.io/pact_broker/webhooks#using-webhooks-with-the-contract_requiring_verification_published-event
GitHub
04/10/2025, 9:40 AMSimon Raess
04/17/2025, 9:10 AMJun Yi
05/13/2025, 9:05 AM--latest
when retrieving the latest published pact version for a consumer/provider, which implies using tags like --latest <branch_name>
.
Given this shift in recommendation, how can I retrieve the latest published pact version for a pacticipant based on the branch name, without relying on tags? Is there a recommended way to achieve this using the Pact Broker CLI?Isaac Richardson
05/20/2025, 1:30 PMpact-broker can-i-deploy
?
I'd like to test using a webhook on a separate branch but is recording a deployment in test environment and then targeting that the best approach or can I target a provider branch specifically?Isaac Richardson
05/20/2025, 1:48 PMThomas Kanne
05/22/2025, 12:27 PMCF-Access-Client-Id
and CF-Access-Client-Secret
with the calls to the Pact-Broker.
In our pipeline we are using the Pact CLI tool which is only sending basic auth token as far as we understood. Same goes for Pact JVM for our unit tests which are communicating with the Pact-Broker.
Do you have any idea how one could solve this issue or is there a feature planned to be able to send custom headers as well?Matt Long
06/17/2025, 8:37 AMAshish Garg
06/19/2025, 12:52 PMStanislav Vodetskyi
06/21/2025, 12:30 AMmy-service
as a name, but I don't think there's a way to map it to a git repo - other than using an external datastore or a service, but nothing built into pact-broker. Is that correct, or am I missing some metadata?