-
Currently, each project must specify both the Pact Broker (or Pactflow) host and any credentials to publish or retrieve pacts.
It would be nice to have a utility (similar to `aws configure` or `travis…
-
Discussion around suitability of a webhook which would report can-i-deploy status to a VCS provider. Probably triggered of a successful provider verification
I’ve just been playing with the github s…
-
Re-using existing provider states can allow a new interaction to be successfully verified without having to make a change to the provider code. It is currently not easy to get a list of all the provid…
-
The Pact Broker now supports branches as first class entities. You can read more about this here: https://docs.pact.io/pact_broker/branches
## Description
Please add support for specifying branch re…
-
Hi!
We're getting a json parsing error when downloading pacts from the latest pact broker versions (e.g. docker image dius/pact-broker:2.6.0-2).
```
com.google.gson.stream.MalformedJsonExceptio…
-
# Pre issue-raising checklist
I have already (please mark the applicable with an `x`):
* [x] Upgraded to the latest Pact Broker OR
* [x] Checked the CHANGELOG to see if the issue I am about to …
-
The current domain model in the Pact Broker supports git branch based workflows, however it does not provide good support for feature toggle based workflows. One example of this is that you can only h…
-
When using the verifier.verify_with_broker method, with a broker usermame containing &, I get the following error:
`'4o' is not recognized as an internal or external command,`. 4o is the rest of the …
-
Hi,
I was wondering. We have the situation that a consumer created a new pact with a new state, which results in a pending pact. This works fine in our pipeline during the junit tests. We can see i…
-
I'm using 5.0.0-beta.1 to send data to pact. In logs there is info "Pact verification successful" but in logs
```
2024-01-26T08:26:23.083017Z ERROR ThreadId(09) pact_verifier::pact_broker: Failed…