Request: Ability to pass json to pact-message via standard in

[TimothyJones]

Pre issue-raising checklist

I have already (please mark the applicable with an x):

• Upgraded to the latest version of the relevant libraries
• Checked to see if the issue has already been raised

Software versions

• pact-ruby-standalone: 1.88.26

Request

Currently, pact-message expects the content JSON to be passed as a command line parameter:

pact-message update MESSAGE_JSON --consumer=CONSUMER --pact-dir=PACT_DIR --provider=PROVIDER

JSON in a command line param is difficult to quote correctly on windows (I haven't found a library that works for all cases yet).

It would be awesome if we could work around this by having the option to pass the content via standard in:

pact-message update MESSAGE_JSON --consumer=CONSUMER --pact-dir=PACT_DIR --provider=PROVIDER
or
echo "$MESSAGE_JSON" | pact-message update --consumer=CONSUMER --pact-dir=PACT_DIR --provider=PROVIDER

[TimothyJones]

Here's a short test:

echo '{ "description": "a test mesage", "content": { "name": "Mary" } }' > msg
cat msg | pact-message  update --consumer=CONSUMER  --pact-dir=. --provider=PROVIDER

[bethesque]

Sounds good.

Why is your example in two steps instead of echo '{ "description": "a test mesage", "content": { "name": "Mary" } }' | pact-message update --consumer=CONSUMER --pact-dir=. --provider=PROVIDER ?

[TimothyJones]

No specific reason, just what I happened to write