pact broker client rewrite is transferred over to the pact-foundation now https://github.com/pact-foundation/pact-broker-cli released to crates/dockerhub/ghcr and available as a github action and has install scripts for windows and unix systems rockon rust

Ideally, we erase/cleanup all references to the old CLI as soon as we can and get everyone onto this amazingness. Before we do that, I guess we need to get it into the wild for a bit more testing? I’m going to raise some tasks in PactFlow also to update to this CLI, which wouldn’t be a bad idea. A few questions (which absolutely should not detract from this glorious work!). Should we also consider updating the following other places that use the old one: 1. Should we package this into the main Docker image (i.e. replace https://hub.docker.com/r/pactfoundation/pact-cli)? a. Or update the pointers to say “this is now deprecated, use the new one here..“? 2. https://github.com/pact-foundation/pact-js-cli 3. Homebrew formula? 4. Should we update the PactFlow GH Actions with the new one also (or wait until these are ? I reckon we could do some updates to our docs, specifically on recommended usage of our CLIs, e.g. • https://docs.pact.io/implementation_guides/cli • https://docs.pact.io/implementation_guides/overview

great questions, some of which worth tabling in a migration issue i reckon Ideally, we erase/cleanup all references to the old CLI as soon as we can and get everyone onto this amazingness

Before we do that, I guess we need to get it into the wild for a bit more testing?

yep, would love to get more testing in. 1. Should we package this into the main Docker image (i.e. replace https://hub.docker.com/r/pactfoundation/pact-cli)? a. Or update the pointers to say “this is now deprecated, use the new one here..“? include pact-broker-cli exe into pact-cli docker image. ultimately replace with consolidated rust cli with all bins embedded in single bin 1. https://github.com/pact-foundation/pact-js-cli should be added to pact-standalone as interim, which would let this be distributed via the js cli, homebrew. 1. Homebrew formula? 2. Should we update the PactFlow GH Actions with the new one also (or wait until these are ? i wonder if we toggle the old/new pact broker client by an env var. opting in makes the pact-broker command use the rust instead of ruby impl

I reckon we could do some updates to our docs, specifically on recommended usage of our CLIs, e.g.

yep on my list to pull in docs, and update guidance, ty