`ignore-order` is not a valid matching rule type

[liwa-datev]

Hi, we stumbeled across the following error when trying to upload pacts.

When trying to upload the following contract:

• pact.json

we observe the following:

$ npm i -g @pact-foundation/pact-cli

$ pact-broker publish *.json --consumer-app-version "0.0.0-SNAPSHOT" --branch "test" --broker-base-url= --broker-token=...

❌ Failed to load pact from JSON: Err(Could not parse matcher JSON Object {"match": String("ignore-order"), "max": Number(0)}

Caused by:
ignore-order is not a valid matching rule type)

$ pact-broker --version
pact-broker 0.6.3

Downgrading the @pact-foundation/pact-cli from 18.0.0 to the next most recent 16.1.7 fixes this problem. So we assume the error sits somewhere in this project, as the backend was changed to this project between these versions.

[YOU54F]

hmm looks like the ignore-order matcher was added to pact-jvm

pact-foundation/pact-jvm@a7375e5

but not to pact-reference, I don't think, there are some

https://github.com/pact-foundation/pact-reference/blob/6680ee104c71836b273fb94f1e5b97a490ee8bad/rust/pact_matching/src/matchingrules.rs#L112-L116

A similar issue was raised in pact-jvm

pact-foundation/pact-jvm#1868

around the pact-stub-server failing on the use of that matcher, which uses the same core engine as the updated pact-cli (which you are using as part of v18)

cc: @rholshausen / @mefellows

[mefellows]

So this implies the publish command checks the pact is valid prior to uploading?

[YOU54F]

we use pact_models to load the pacts, pull out the consumer/provider names, and merge duplicate interactions.

validation is opt in, this code this hits is later on, if validate was on, it would have been caught earlier

https://github.com/pact-foundation/pact-broker-cli/blob/bc25f0a8bca1fd15b5fda4f8284c03cd4a1016f9/src/cli/pact_broker/main/pact_publish.rs#L347