Hey folks :wave: our provider framework uses the P...
# pact-python
j
Hey folks 👋 our provider framework uses the Pact-Python library, we've started seeing some builds passing with the Pending Pact feature - we'd currently like these to fail so the build fails As far as I can tell the Pact Pending feature is meant to be off by default and I can't see anywhere that I'm enabling it, can anyone confirm if that's the case please? Or if not, how I can disable it
m
It should be, what version of the broker are you on? I believe it was a default on for a few minor versions before it was set to off by default
I'd suggest jumping to latest version of broker. If not that's not, it might be the version of python is not explicitly setting the flag as false
j
So looks like the broker is on
Pactflow Version: 85e7754e3
(it's not self-hosted so not sure if we can even control the version) The verifier runs from a Docker container using
FROM --platform=linux/amd64 python:3.7
- is there a way to explicitly set the flag?
👍 1
m
Thanks. So you'd be on the latest if Pactflow. I'm guessing something like pending = False
Worth checking if there are any related issues on GitHub.i can follow up tomorrow otherwise
j
Looks like this could be related: https://github.com/pact-foundation/pact-python/issues/264
The Pact Broker now defaults to true if the includePendingStatus field is not set
I'll have a look at that and see if that sorts it 👍
👍 1
m
Ah that rings a bell
j
After a version bump and a bit of digging it looks like
--no-enable-pending
is what I was after, think that's it sorted now Cheers for the help Matt 👍
🙌 1