participantVersion and latest are not mutually exclusive in CanDeploy

Hello friends, I’m happy to use Pact!

I’ve noticed something in how pact-node parses the options to can-i-deploy.

Software versions

• Library version:
  • @pact-foundation/pact-node ^8.1.2

Expected behavior

I think pact can-i-deploy command and CanDeploy should allow me to check whether I can deploy current service against the specified tag without specifying a version.

Actual behavior

I’m using the Broker credentials from Pact Workshop to illustrate this:

npx pact can-i-deploy
        --participant 'Our Provider' \
        --latest prod \
        --pact-broker https://test.pact.dius.com.au \
        --username dXfltyFMgNOFZAxr8io9wJ37iUpY42M \
        --password O5AIZWxelWbLvqMd8PkAVycBJh2Psyg1

Error: Missing option --participant-version.

I might be wrong, but I think this is incorrect behavior. 🤔

These checks https://github.com/pact-foundation/pact-node/blob/master/src/can-deploy.ts#L50 should be checking if latest is specified and not require participantVersion in that case.

I can work on the PR to change this.

What do you think?

[TimothyJones]

This is released in pact-node 10.0.0, which is a breaking change to the way options work. See the changelog for more details

[halfzebra]

Thanks for the update!