Hi,
why is the PactVerfier trying to get the pacts...
# pact-netg
Guido Sprenger
11/21/2022, 4:06 PMHi,
why is the PactVerfier trying to get the pacts from the wrong path here?
My PactBroker is running at "https://foo.bar.cloudapp.azure.com/pactiobroker" and I configured the brokerBaseUri in my pact-net test to that exact path.
Why is it doubling the "/pactiobroker" part in the request?
m
Matt (pactflow.io / pact-js / pact-go)
11/21/2022, 10:18 PM
I think you’re hitting this issue: https://github.com/pact-foundation/pact-reference/issues/220
👍 1
g
Guido Sprenger
11/22/2022, 8:28 AMThanks for the hint. I guess there is nothing I can do in the .NET-Library at least?
m
Matt (pactflow.io / pact-js / pact-go)
11/22/2022, 8:46 AM
Not yet. My advice is to not use a context path for now (but my guess is that’s not an option?)
Matt (pactflow.io / pact-js / pact-go)
11/22/2022, 8:47 AM
Or, if you’re up for fixing the bug - we’d appreciate a PR!
g
Guido Sprenger
11/23/2022, 9:49 AMOK, I got rid of the context path. Fixing the bug would be in the PactBroker internals (Rust)?
m
Matt (pactflow.io / pact-js / pact-go)
11/23/2022, 10:56 AM
It’s in the client, which is a shared library written in Rust (not the broker, which is Ruby)
Matt (pactflow.io / pact-js / pact-go)
11/23/2022, 10:56 AM
If you’re up for a small PR to a rust lib, we’d appreciate it!
4 Views