Ruby pact-provider-verifier --enable-pending returns non-zero exit code if pending pact provider state setup fails

[StefanSmithGousto]

Observed behaviour

The Ruby pact-provider-verifier tool (with --enable-pending on) returns a non-zero exit code if POST to Provider States Setup URL responds with a 500 status when verifying a pending pact.

Expected behaviour

The --enable-pending flag should suppress both verification and provider state setup failures for pending pacts. It only seems to suppress the former. This means a consumer can break a provider's mainline build if they define an unsupported provider state.

Work arounds

One solution would be for the provider to gracefully handle unsupported provider state but we'd rather see these failures published to our Pact Broker so the consumer is aware of the root cause of verification failure. That is the current behaviour (great!) but we'd like this to happen without blocking the Provider's pipeline.

[bethesque]

Thanks Stefan. I'll look into this for you.

[bethesque]

Sorry Stefan, this dropped off my radar. I'll try and get on to this.