The link to `Publishing` under Pact JS here is bro...
# pactflowj
Joel Whalen
11/03/2023, 1:22 PMThe link to
PublishingJoel Whalen
11/03/2023, 1:24 PMor I assume we are to just use the broker CLI here? https://docs.pact.io/pact_broker/client_cli/readme
y
Yousaf Nabi (pactflow.io)
11/03/2023, 1:33 PM
Apologies about that!
Yes its generally recommend to use the standalone cli tools 👍
If you are using pact-js, it contains pact-js-core, which exposes the cli tools as npm bin stubs
https://github.com/pact-foundation/pact-js-core?tab=readme-ov-file#cli-tools
there is also an api exposed for programatic use, but I wouldn’t recommend that approach now, as we are more than likely due to deprecate that in the future.
The bin stubs will be exposed in https://github.com/pact-foundation/pact-js-cli which is still due to be published (just a wrapper over the cli tools) - not sure if we should expose the programmatic api here as well (I think we would rather avoid it, to avoid maintainence efforts)
Will look to sort those links so they point to the relevant bits
j
Joel Whalen
11/03/2023, 1:52 PMSince we use nodejs in our backend along with docker compose, the docker cli solution works perfectly actually
🙌 1
Joel Whalen
11/03/2023, 1:52 PMthanks for clarifying though!
b
boden winkel
01/23/2024, 2:08 PM@Joel Whalen did you have any problem with mounting volume using docker cli approach ?
boden winkel
01/23/2024, 2:10 PMdocker run --rm \
-w $(Build.SourcesDirectory)/$(bffFolder)/src/pacts \
-v $(Build.SourcesDirectory)/$(bffFolder)/src/pacts:$(Build.SourcesDirectory)/$(bffFolder)/src/pacts \
-e PACT_BROKER_BASE_URL="url" \
-e PACT_BROKER_TOKEN="token" \
pactfoundation/pact-cli:latest \
publish \
$(Build.SourcesDirectory)/$(bffFolder)/src/pacts/pact.json --consumer-app-version=$(version.packageSemVer)
this command is nor working for me, saying that file does not have permissions..
boden winkel
01/23/2024, 2:15 PMIm tyring to run it in azure devops pipeline
j
Joel Whalen
01/23/2024, 2:33 PMIf CI doesn't have write permissions, you need to give it permission to write to that file or folder. I don't know how to configure that in Azure, but I'm sure they have documentation for that.
As for docker volumes, I was using docker compose and put my API as one service, and the pact cli image as another service. Then in the highest level of the docker compose file, you want to define a shared volume between the two like so:
volumes:
my-shared-volume:
Then define 'my-shared-volume' in each services volumes key