@Beth (pactflow.io/Pact Broker/pact-ruby) Hi, ive noticed I'm unable to merge things without having approvals. not sure if this is because of an overarching org policy. i dont think im able to change it on the repo level either https://github.com/pact-foundation/pact-broker-chart/pull/16

Hello 👋 just sharing a feature request I have raised as was forced to add legacy tagging as a workaround to get what i need (provider version number in a specific environment) https://pact.canny.io/feature-requests/p/get-latest-provider-version-for-a-specific-environment

Hello. I would appreciate some help with the errors below. I am new to pact and I am trying to publish my consumer test pact to the broker but

win32-1.89.02-rc1\pact\bin\pact-broker.bat

is missing from

node_modules\@pact-foundation\pact-node\standalone\

. I am using pact-node -v

^10.17.6

personal-media@0.1.0 test:publish
node publish.js

[2022-11-28 17:55:35.334 +0000] INFO (13664 on DESKTOP-1H0P31U): pact-node@10.17.6: Publishing Pacts to Broker
[2022-11-28 17:55:35.336 +0000] INFO (13664 on DESKTOP-1H0P31U): pact-node@10.17.6: Publishing pacts to broker at: <https://cloudmargin.pactflow.io>
[2022-11-28 17:55:35.368 +0000] ERROR (13664 on DESKTOP-1H0P31U): pact-node@10.17.6: spawn C:\Users\sanmi\OneDrive\Desktop\New folder\personal-media\node_modules\@pact-foundation\pact-node\standalone\win32-1.89.02-rc1\pact\bin\pact-broker.bat ENOENT
    Error: spawn C:\Users\sanmi\OneDrive\Desktop\New folder\personal-media\node_modules\@pact-foundation\pact-node\standalone\win32-1.89.02-rc1\pact\bin\pact-broker.bat ENOENT
        at notFoundError (C:\Users\sanmi\OneDrive\Desktop\New folder\personal-media\node_modules\cross-spawn\lib\enoent.js:6:26)
        at verifyENOENT (C:\Users\sanmi\OneDrive\Desktop\New folder\personal-media\node_modules\cross-spawn\lib\enoent.js:40:16)
        at ChildProcess.cp.emit (C:\Users\sanmi\OneDrive\Desktop\New folder\personal-media\node_modules\cross-spawn\lib\enoent.js:27:25)
        at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
[2022-11-28 17:55:35.369 +0000] WARN (13664 on DESKTOP-1H0P31U): pact-node@10.17.6: Pact exited with code 1.
[2022-11-28 17:55:35.370 +0000] ERROR (13664 on DESKTOP-1H0P31U): pact-node@10.17.6: Pact publication failed with non-zero exit code. Full output was:       
The system cannot find the path specified.

Pact contract publishing failed:  Error: Pact publication failed with non-zero exit code. Full output was:
The system cannot find the path specified.

    at ChildProcess.<anonymous> (C:\Users\sanmi\OneDrive\Desktop\New folder\personal-media\node_modules\@pact-foundation\pact-node\src\publisher.js:79:40)   
    at Object.onceWrapper (node:events:510:26)
    at ChildProcess.emit (node:events:402:35)
    at ChildProcess.cp.emit (C:\Users\sanmi\OneDrive\Desktop\New folder\personal-media\node_modules\cross-spawn\lib\enoent.js:34:29)
    at maybeClose (node:internal/child_process:1064:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
 *  Terminal will be reused by tasks, press any key to close it.

Hi, Can someone please help me identify what the issue is, I have published my consumer contract to the broker, but when i try to verify the provider i get the following. I have also attached a copy of my provider.js file

22:42:05.290] INFO (26840): pact@10.1.4: Verifying provider

[22:42:05.297] INFO (26840): pact-core@13.12.2: Verifying Pacts.

RUNS  __tests__/provider.js

RUNS  __tests__/provider.js

2022-11-29T22:42:11.622800Z ERROR ThreadId(12) pact_verifier: Failed to load pact - Failed to load pact '<https://cloudmargin.pactflow.io/pacts/provider/Provider-Backend/consumer/Consumer-Personal-Media/latest>' - Request failed with status - 401 Unauthorized

2022-11-29T22:42:11.624057Z ERROR ThreadId(12) pact_verifier: Failed to load pact - Could not load pacts from the pact broker '<https://cloudmargin.pactflow.io>'

2022-11-29T22:42:11.625595Z  WARN ThreadId(12) pact_matching::metrics:

Please note:

We are tracking events anonymously to gather important usage statistics like Pact version and operating system. To disable tracking, set the 'PACT_DO_NOT_TRACK' environment variable to 'true'.

Failures:

1) Failed to load pact - Failed to load pact '<https://cloudmargin.pactflow.io/pacts/provider/Provider-Backend/consumer/Consumer-Personal-Media/latest>' - Request failed with status - 401 Unauthorized

2) Failed to load pact - Could not load pacts from the pact broker '<https://cloudmargin.pactflow.io>'

FAIL  __tests__/provider.js (7.98 s)

Backend Personal Media verification

× validates the expectations of personal media (6414 ms)

● Backend Personal Media verification › validates the expectations of personal media

Verfication failed

at node_modules/@pact-foundation/pact-core/src/verifier/nativeVerifier.ts:50:20

Hi, how to do a tag a contract with the PR branch from the mvn command when publishing it? Can’t find the right syntax for that. Not sure if something like this?

./mvnw -Dpactbroker.auth.token=${pactBrokerToken} -Dpactbroker.tags=${getTag(testEnvt)} -Dtest=com.hmhco.lti.ags.tool.infrastructure.pact.*IT \
-Dpact.consumer.version=${ReleaseVersion} integration-test

I am interested in adding pact-plugins to my broker server. just copying the pact_plugins to the broker is enough? Does anyone have some steps followed for the broker to run the plugins (especially mockServer capable) ones? it would be great help to interact and learn from you.

Hi guys. Please enighten me on how should I instruct the provider to run the test against a specific version of the contract and not against the newest contract published in the broker. My Pact broker initially had a contract version that was successfully passing the tests. But then, the team that owns the consumer pushed from their branch a new version of the contract, and the provider tests are failing now, because they run against the latest contract in the Matrix list (contracts in the Matrix are sorted by database id I assume). How can I make the provider tests run against the latest "prod" version of the contract and not against versions published by dev branches? (against c.v.1-PROD according to the screenshot instead of c.v.2.-WorkInProgress) Thank you!

message has been deleted

P..S.: to make it clear, I don't want to block provider releases as long as consumer's new version is not in master yet

Hi, I had a question about whether there is an override for this behaviour. For a provider, I have been running can-i-deploy as a way of checking if verifications exist between my current branch and ‘main’ branch consumers and then through the deployment lifecycle checking if there are verifications between environments. I recently cleared down contracts to test what would happen with custom webhooks when the consumer runs can-i-deploy to trigger the provider (it worked fine). The problem I had was when the provider was deployed to a later environment than the consumer, where no contracts existed between them. I can understand the usecase of failing can-i-deploy if the contracts were unverified as interactions would be required but what about where the are no consumers in the environment for a provider. is that a breaking case? So my question is…is there a flag to say “don’t fail if there are no consumers of this tag/environment” so it only fails if the contract has changed and there has previously been a verification for the tag and/or environment but not for this latest version

The GitHub user bethesque has signed out. Use the following command/s to recreate subscriptions /github subscribe pact-foundation/pact_broker /github subscribe DiUS/pact_broker-docker

/github subscribe pact-foundation/pact_broker

/github subscribe pact-foundation/pact-broker-docker

/github unsubscribe pact-foundation/pact_broker

/github subscribe pact-foundation/pact_broker issues pulls releases deployments

/github unsubscribe pact-foundation/pact_broker commits

/github unsubscribe pact-foundation/pact-broker-docker commits

Hi guys! Running a

pact-broker help

returns the entire list of commands that can be executed, which is useful. But for some commands in the list, the parameters are truncated (due to space maybe). E.g.:

pact-broker publish PACT_DIRS_OR_FILES ... -a, --consumer-app-version=CONSUMER_APP_VERSION -b, --broker-base-url=BROKER_BASE_URL

Also, on the releases page in github I can only see the Usage for

pact-mock-service

,

pact-stub-service

and

pact-provider-verifier

Can we get an implementation for the entire list of attributes when running for example

pact-broker publish help

? - (which at the moment returns No value provided for required options '--consumer-app-version') Thank you,

Hey folks, I'm experiencing some problems with pact provider verification via the new ``contract_requiring_verification_published`` webhook. My pact broker is hosted on sh1989.pactflow.io The error I receive is:

pact_1 | bundler: failed to load command: /pact/bin/pact (/pact/bin/pact)

pact_1 | /usr/lib/ruby/gems/3.0.0/gems/pact-1.63.0/lib/pact/hal/entity.rb53in `_link!': Could not find relation 'pb:latest-provider-pacts' in resource at https://sh1989.pactflow.io/pacts/provider/pact-provider/consumer/pact-consumer/pact-version/70a8e3b23699154f9342895ea8bac8e8d79396e3/metadata/Y3ZuPWRmMTgwMmI2Jnc9dHJ1ZQ (PacthalRelationNotFoundError)

Hello team!, I'm new on Pact and I'm performing a PoC with Pact. I've created 3 dummy services with Java. I've also used the Pact broker docker image to set up a container in my local. Currently I've been able to generate contracts from the consumer side and publishing into the broker and also verify the providers and publish the verificarion into the broker. At this point I want to play with the Docker Pact CLI (pactfoundation/pact-cli). I couldn't execute any command at this point because a TCP connection error with the pact-broker is raised.

Example command

docker run --rm pactfoundation/pact-cli:latest \
pact-broker list-environments -b="<http://localhost:9292>"

Error

Error making request - Errno::EADDRNOTAVAIL Failed to open TCP connection to localhost:9292 (Address not available - connect(2) for "localhost" port 9292) /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/hal/http_client.rb:79:in `block in perform_request', attempt 3 of 3
Error retrieving matrix. Errno::EADDRNOTAVAIL - Failed to open TCP connection to localhost:9292 (Address not available - connect(2) for "localhost" port 9292)

If I perform a curl

<http://localhost:9292>

works fine. Do you know If I need some kind of configuration or am I doing something wrong with the Pact CLI?

I don't find a clear list in the docs, is this the list of all native webhook events?

events << 'contract_content_changed' if options.contract_content_changed
                events << 'contract_published' if options.contract_published
                events << 'provider_verification_published' if options.provider_verification_published
                events << 'provider_verification_succeeded' if options.provider_verification_succeeded
                events << 'provider_verification_failed' if options.provider_verification_failed
                events << 'contract_requiring_verification_published' if options.contract_requiring_verification_published

https://github.com/pact-foundation/pact_broker-client/blob/bf58b5c6503bdf6a4e13743[…]f12d83af3e049891/lib/pact_broker/client/cli/webhook_commands.rb

Hi Team 👋, We are using postgressql v11.16 and want to upgrade the version to 14.6 is there anything which can break or any pointers to keep an eye on thanks

#92 Upgrade to at least ruby:2.7.6-alpine3.16 Issue created by jorander Pre issue-raising checklist I have already (please mark the applicable with an

x

): ☑︎ Confirmed this is the right place to raise the issue - only issues related to the Dockerization of the Pact Broker should be raised here. Issues related to the Pact Broker application itself should be raised in the Pact Broker project. ☑︎ Upgraded to the latest Pact Broker Docker image OR ☑︎ Checked the </CHANGELOG.md|CHANGELOG> to see if the issue I am about to raise has been fixed ☑︎ Read the Troubleshooting page Software versions • pact-broker docker version: 2.105.0.1 Expected behaviour No known vulnerabilities. Actual behaviour Image apline3.15 contains three packages with known vulnerabilities that are all fixed and upgraded in alpine3.16: • gdbm: fixed in gdbm-1.23 • sqlite: CVE-2021-46100 (not disclosed but seems to be fixed in ver 3.37.0) • icu-libs: fixed in version 71.1-rc2 Steps to reproduce Security scan provided by Jfrog Xray. Relevent log files N/A pact-foundation/pact-broker-docker

#93 Upgrade Bundler to at least 2.2.33 Issue created by jorander Pre issue-raising checklist I have already (please mark the applicable with an

x

): ☑︎ Confirmed this is the right place to raise the issue - only issues related to the Dockerization of the Pact Broker should be raised here. Issues related to the Pact Broker application itself should be raised in the Pact Broker project. ☑︎ Upgraded to the latest Pact Broker Docker image OR ☑︎ Checked the </CHANGELOG.md|CHANGELOG> to see if the issue I am about to raise has been fixed ☑︎ Read the Troubleshooting page Software versions • pact-broker docker version: 2.105.0.1 Expected behaviour No known vulnerabilities. Actual behaviour Bundler 2.1.4 contains two vulnerabilities fixed in later versions (at least version 2.2.33): • https://bundler.io/blog/2021/02/15/a-more-secure-bundler-we-fixed-our-source-priorities.html • GHSA-fj7f-vq84-fh43 Steps to reproduce Security scan provided by Jfrog Xray. Relevent log files N/A pact-foundation/pact-broker-docker

#94 Can MariaDB be removed from list of dependencies? Issue created by jorander Pre issue-raising checklist I have already (please mark the applicable with an

x

): ☑︎ Confirmed this is the right place to raise the issue - only issues related to the Dockerization of the Pact Broker should be raised here. Issues related to the Pact Broker application itself should be raised in the Pact Broker project. ☑︎ Upgraded to the latest Pact Broker Docker image OR ☑︎ Checked the </CHANGELOG.md|CHANGELOG> to see if the issue I am about to raise has been fixed ☑︎ Read the Troubleshooting page Software versions • pact-broker docker version: 2.105.0.1 Expected behaviour No known vulnerabilities. Actual behaviour The documentation for setting up database connectivity describes PostgreSQL (for production) and SQLite (for testing), but it doesn't mention MariaDB. Still the

mariadb-dev

package is brought in as a dependency in the Docker image. MariaDB version 10.6.10 seems to have quite a few security issues, some not fixed in later versions either. • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-27385 • https://jira.mariadb.org/browse/MDEV-26911 • https://jira.mariadb.org/browse/MDEV-27001 • https://jira.mariadb.org/browse/MDEV-26956 • https://jira.mariadb.org/browse/MDEV-26589 • https://jira.mariadb.org/browse/MDEV-26590 • https://jira.mariadb.org/browse/MDEV-26556 • https://jira.mariadb.org/browse/MDEV-26561 • https://jira.mariadb.org/browse/MDEV-26574 Question: Is MariaDB used for some internal tasks, or could it be removed from the pact-broker-docker image? Steps to reproduce Security scan provided by Jfrog Xray. Relevent log files N/A pact-foundation/pact-broker-docker

What is the proper way to query can-I-deploy with multiple services? pact-jvm seems to only support checking single pacticipant, HAL browser also only shows request builder for only one pacticipant. I know it can be done with Pact CLI but most of my CI code is written in Java and I would much more prefer to just send raw REST request rather than add dependency on external CLI.

Hi, Happy New Year! 🙂 I am trying to setup webhooks. I have created a webhook using the docker-cli but when I test the webhook it fails due to

{"message":"Exception obtaining parameters","status-code":500}

I have checked the logs for clues and searched the source code to trace the error message but to no avail. Any help appreciated!

Hello, Happy New Year! Is there way to link the broker to the pipeline/job that gave publish a result ?