Feature Request: Create binstubs for pact-standalone binaries
See original GitHub issueAS a user who wants to integrate to the latest Pact CLI features
IT would be useful to be able to easily reference the Pact binaries (e.g. pact
, pact-broker
pact-message
etc.)
SO that I can use them without having to write JS wrappers, or wait for them to be included in the JS library
Example use case
Prior to deployment, we often run the can-i-deploy
tool to check if it’s safe to release either a consumer or a provider. Bash is an appropriate tool for this. It’s hard to find the CLI tools if you don’t know what you’re doing, but it is possible:
package.json:
"can-i-deploy:consumer": "$(find ./node_modules -name pact-broker | grep -e 'bin/pact-broker$' | head -n 1) can-i-deploy --pacticipant SNSPactEventConsumer --latest --broker-base-url https://test.pact.dius.com.au --broker-username xxx --broker-password yyy",
Typically, I just install the CLI tools into my Docker container and add them to the path. But it would be nice if I could just go:
package.json:
can-i-deploy:consumer": "pact-broker can-i-deploy --pacticipant SNSPactEventConsumer --latest --broker-base-url https://test.pact.dius.com.au --broker-username xxx --broker-password yy
I imagine the ./node_modules/.bin
dir might look like:
ls ./node_modules/.bin
pact_broker -> ./node_modules/@pact-foundation/pact-node/standalone/darwin-1.33.1/bin/pact-broker
pact -> ./node_modules/@pact-foundation/pact-node/standalone/darwin-1.33.1/bin/pact
...
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:9 (5 by maintainers)
Top GitHub Comments
Yes, I could try, it would be my first github PR though. I am reading the contribution guidelines now.
I think this is now fixed by #161 (thanks @mefellows! Much appreciated!)