Hey Pact folks and happy new year I ve followed the README f Pact Foundation #pact-go

Hey Pact folks, and happy new year! I’ve followed ...

Will Herring

01/03/2023, 11:54 AM

Hey Pact folks, and happy new year! I’ve followed the README for pact-go that talks about installing the standalone CLI tools, and adding their location to the PATH var. I’ve also cloned the

pact-workshop-go

repo, and if i run

make consumer

in there, everything runs okay, and the contract is generated, but I’ve tried doing the same thing for one of our own services, and whenever I try to run the consumer test there, I get an error saying that the CLI tools are out of date. Currently running on an M1 Mac. I’ve since tried using the

pactfoundation/pact-cli

docker image, and that seems to at least read the test, but just wondering if there’s anything obvious I’ve missed from the standalone CLI installation, or what the recommended setup would be for an M1 Mac.

👋 1

Matt (pactflow.io / pact-js / pact-go)

01/03/2023, 11:17 PM

Hi Will, happy new year to you too!

Matt (pactflow.io / pact-js / pact-go)

01/03/2023, 11:18 PM

First up, I'd recommend jumping straight to the 2.x.x release. It's close to stable now and has more features and better support

Matt (pactflow.io / pact-js / pact-go)

01/03/2023, 11:24 PM

The fact the workshop project works tells me it's likely you haven't got the tools properly added to the path and the runtime is unable to find the binaries. But with 2.x.x there is no dependency on the standalone (which won't natively run on M1 outside of Rosetta, btw). The docker image can then be used for publishing etc (albeit really that's a CI only thing anyway)

Will Herring

01/04/2023, 9:30 AM

Thanks a lot Matt, appreciate your help, will take a gander at the 2.x.x releases and see where I get to.

👍 1

2 Views

Open in Slack

Previous Next