This channel will receive notifications from pact-foundation/pact_broker for:

releases

,

deployments

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

This channel will receive notifications from pact-foundation/pact-broker-docker for:

pulls

,

releases

,

deployments

/github unsubscribe pact-foundation/pact_broker pulls

This channel will receive notifications from pact-foundation/pact_broker for:

releases

,

deployments

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

This channel will receive notifications from pact-foundation/pact-broker-docker for:

pulls

,

releases

,

deployments

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

This channel will receive notifications from pact-foundation/pact-broker-docker for:

releases

,

deployments

Good afternoon. This is Chandra. I am working on a POC to implement the http based pact tests using pactnet 4.x. I am using Teamcity for CI pipelines and pactflow pact broker (trial version) to implement 'Contract published that requires verification' webhook event. The webhook event is getting fired when a changed contract file is published and in turn triggering the provider build on Teamcity. I want to pass the '${pactbroker.pactUrl}' in pactflow pact broker to provider build pipeline on Teamcity. As we need this in provider verification tests to verify the specific changed contract file and publish the results back to pact broker. Can someone please help me with this ? Screenshots for the webhook event and the provider builds:

When we PUT the pact to with a powershell script, we set the uri as

$version = 1.0.0.0
$buildId = $(Build.BuildId)   # e.g. 12345
$uri = "$brokerUri/pacts/provider/$provider/consumer/$consumer/version/$version_$buildId"

I was expecting the version to be 1.0.0.0_12345 but in the broker the consumer version is shown only as 12345. At https://docs.pact.io/pact_broker/pacticipant_version_numbers i read

When publishing a pact or a verification, the resource is associated with a particular version of the pacticipant (application), which is identified by a version number. Just to make it very clear - the version number that is specified in the URL of a pact or a verification is the application version number, not the pact version. Pact versioning is done for you behind the scenes by the Broker, and is based on the content of the pact.

How do I set the pact version? I don't see any version reference in my c# source using PACT.V3 (I know i need to upgrade to V4) Thanks

Hi! I am trying to run pact broker at a different context-path other than / and trying that using below nginx conf

server {

listen      80 default_server;

server_name localhost:9292;

location / {

rewrite ^(.*)$ /pact$request_uri permanent;

}

location /pact {

proxy_pass <http://localhost:9292>;

proxy_set_header Host $host;

proxy_set_header X-Real-IP $remote_addr;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

}

}

Even after mutiple tries, its showing up the broker page on / and /pact is giving a 404. Do I need to change any other configs to configure the web server?

Hello! I am trying to understand how the environment is set for the pacts published in the broker (I'm using pactflow). Is it through

record-deployment

?

Hello again. Can anyone describe how the "for-verification" list gets produced for a registered pacticipant. e.g. url. https://your-broker/pacts/provider/provider-microservice/for-verification What we are seeing is, this list is missing certain consumers. Our consumer selectors are ONLY querying

mainBranch: true

Our consumer microservices mainBranch are set to

main

. There is a contract for the version on main. Yet the "for-verification" list is missing microservice(s). In the broker UI, the consumer is listed along with its providers. However, a query of "latest version from branch..."

main

returns no results. So we are a bit confused. Thanks for any help. PS: The only way I've been able to resolve this issue, is to delete the consumer pacticipant completely from the broker, and run the CI pipelines again.

Hi All, Quick question:

contract_requiring_verification_published

event will trigger when consumer publish contract for the first time? As per the documentation, the event would get triggered when consumer publishing the contract for the first time, but when I am publishing I can see only two events are triggering, which are

contract_published

,

contract_content_changed (first time untagged pact published).

Can some please help me what I might have missed in my consumer service configuration? Note: _If provider already verified with

main branch

or

deployed/released

then the

contract_requiring_verification_published

event is getting triggered._ Here are the documentation links which I was referring: https://docs.pact.io/blog/2021/10/11/contract-requiring-verification-published-webhook-event https://docs.pact.io/pact_nirvana/notes_1 #pact-broker

Hi All, is there a way to install pact-broker in k8s with HELM and configure it to skip the ingress installation ?

@Ruth has left the channel

Hello 🙂, Hopefully just a quick question. Can a PactBroker communicate on a private network via private endpoints? At my company, we're exploring pact broker connectivity. If we set the web app to public we can access the pact broker, however setting it to private returns a forbidden response. Is there any app config settings we need to be aware of for network connectivity? We've followed the pact docs to spin a pact broker up. My ops team have looked at the network side of things and cannot see any firewall or other network issues. So we're a bit confused and are looking for guidance to help move things along 🙂. Any help would be greatly appreciated and thank you for your support! 🙂

I have a proposal for simplifying WIP pacts that I'd appreciate feedback on https://github.com/pact-foundation/pact_broker/discussions/640

Hi! I got some question about the CICD of pact broker, according to docs: The consumer CI build generates the pacts during execution of its isolated tests, and then publishes the generated pacts. The provider CI retrieves the pacts, performs the verification locally, and then publishes the verification results back to the broker. Does this means the consumer CI needs to notice provider CI that the pact is generated please verify it? Does it like event-bridge structure or something else?

Hello team, I am getting an issue that in one validation some of contracts published successfully and some of them can’t be published and response status is 403. I am confused because it’s in one service and there is no difference in the configuration. Have anyone experience same issues and have a resolution?

Hi folks, I'm trying to install pack-broker via helm chart with minikube from here but I can see some errors in the pact broker pod

│ /pact_broker/vendor/bundle/ruby/3.2.0/gems/pg-1.5.3/lib/pg/connection.rb:696:in `async_connect_or_reset': connection to server at "10.111.189.45", port 5432 failed: Connection refused (PG::ConnectionBad)                                                                                                              │
│     Is the server running on that host and accepting TCP/IP connections?

Then, I can also see that the

pact-broker-postgresql

fails with the following error message

2023-11-09 20:10:56.490 GMT [141] FATAL:  password authentication failed for user "bn_broker"                                                                                                                                                                                                                            │
│ 2023-11-09 20:10:56.490 GMT [141] DETAIL:  Connection matched pg_hba.conf line 1: "host     all             all             0.0.0.0/0               md5":

I've checked the README.md and try with both approaches but with no luck • Automatic Database Credential Creation • Specifying Password for PostgreSQL to Use

Hi. When browsing to

<http://yourbroker/integrations>

the page displays a Response Body that appears to be JSON. However, when I

curl

to this url, the response I get back was surprising. Its formatted plaintext. Graphviz? Is there any way of getting this back in JSON format? It would be much better for scripting, if it was JSON. Thanks

is there a way to see which version is rolled out to which environment? I can’t seem to figure it out. I’ve played with

describe-environment

describe-pacticipant

and

describe-version

and none seem to have the info I need. I’d love to see a table like

| Version | Environment |
| UUID    | ENV1        |
...

This message was deleted.

Would there be an issue if we somehow published verification results of an earlier provider version later than the latest provider version? E.g. someone manually reran a failed CI/CD step in an earlier build and published the verification results along with it. Pact broker would treat this as "latest" even though it's not your latest software version.

Hi there, I'm reading about using an external database and I came across this section

Specify Credentials via Secret
Configure the Pact Broker to use an existing Secret to retrieve the user password as a means to connect to the database. Ensure that the Kubernetes Secret has the password in the user-password field and ensure that you have set externalDatabase.config.auth.existingSecret value to the name of the secret. To configure the username, you can use the username value.

In my situation, I'm provided with a secret that contains the encoded db password among other db details. The issue is that the field doesn't match

user-password

and unfortunately it cannot be changed as it's used across different areas. Is there any way I can map the field name to the required one so that I can use the right external db configuration?

is it possible to ignore missing verifications during

can-i-deploy

to a given environment? we have a provider that’s rolled out (recorded) to our integration environment but not production, and as a result it’s blocking our production rollouts (even if we don’t use the provider --yet-- in production)

oh, cool,

--ignore=

works

ignore me 👍