Now, I'm going to run my pipeline for the dev and master branches of the consumer (who like the provider are based on the same commit). What I EXPECT to see is that there are two separate entries one for dev + master provider to dev + master consumer, and one for test provider to dev + master consumer. HOWEVER, instead, I see a single entry for the test provider to the dev + master consumer and the dev + master provider contract has just... disappeared. Even weirder, the matrix page just shows a non-entry for the provider columns. What's going on here?

Hello 👋 we're looking at using bi-directional contracts for events in javascript and python using pactflow. I didn't completely understand the rough timescales on the roadmap, where does it sit?

hi, we're trying to implement BDCT and are a bit confused how to publish the provider contract with the appropriate tags, branch and env. I followed this doc but the contract uploaded doesn't have any branch info and not sure how to pass it in. https://docs.pactflow.io/docs/bi-directional-contract-testing/contracts/oas#publishing-the-provider-contract--results-to-pactflow.

Hi team. just trying the free version packflow. the page link to how to publish contract is not accessible. https://docs.pactflow.io/docs/bi-directional-contract-testing/publishing/

👋 Hello everybody, Have you tried to publish a Pact or Provider contract to the Pactflow platform and been unsuccessful? Got an account but not tried it out yet? Drop me a reply in a 🧵 and we'll see if we can get you sorted!

My first question - when I look at the matrix tab for an integration, I see a list of consumer versionsbut I don’t see any provider details, for example:

My second question is more of a feature request - we’re currently evaluating how we could make the OpenAPI specs available in SwaggerUI format to act as a human-readable API repository. I see that Pactflow can already render SwaggerUI for each provider contract - it would be great if it could serve up an index page that shows each provider and has a link to the latest version of its OpenAPI spec.

Hi! we are also new to Pactflow here, and we are trying to work in our first POCs using it, in this case, for the consumer side with cypress. However, following the existing sample project I am coming with the issue that if I

intercept

the endpoint and then use

cy.visit

in the test I get the following error:

The `content-type` of the response we received from your web server was:

  > `application/json`

This was considered a failure because responses must have `content-type: 'text/html'`

I can set at the endpoint the header

{ 'Content-Type': 'text/html' }

and the ignore it, in that case it doesn't fail and publish the contract, nevertheless it will fail when checking against the provider as the response is sent as string. Is there a way to workaround this or I am missing something here?

Is pending enabled?

Hello. Im having trouble getting my pact verified by the Provider using pactflow. The configuration is junit5+spring jvm. I can get the consumer pact uploaded to the pactflow fine, but when i run the verification test on the Provider i get Connection refused. Im using the token for @PactBrokerAuth. Is there any troubleshooting tips anyone can recommend?

It’s may a silly question but what exactly does it mean to have 5 contracts in the Starter Free packet? Interactions or pact files? I would understand that I can write 5 pact files for 5 endpoints. One endpoint = one pact file which can have more then 5 interactions, right? Or is a contract = one interaction in a pact file? :)

Hello, I have a question/issue that I just noticed today. Whenever out consumer app publishes a new pact, the webhook fires in Pactflow and kicks off a build to verify the pact in the provider. But I notice that its firing multiple times. This is causing our contract tests to take up more build agents than necessary, and I can see this turn into an issue in the future once we start to adopt pactflow more widely. Has anyone else seen this?

Hi, I’ve switched my webhooks to run only on

contract_requiring_verification_published

to help reduce the amount of builds we run. When I’m sending across the trigger pipeline my payload body contains CONSUMER_TAGS, PACT_CONSUMER and PACT_URL. Now I’ve just been reading through the documentation around

contract_requiring_verification_published

and I’ve noticed that you’ve mentioned I need to pass in

${pactbroker.providerVersionNumber}

and

${pactbroker.providerVersionBranch}

. I was wondering what would be possible issues I would face by not including these values in my webhook payload? It seems to be working currently

Hello there! This question is more of a conceptual one, as I'm trying to get my head around the best implementation of pact for my use case. The project I'm working on is looking to implement a microservice design, but most of the services will be reliant on 3rd party APIs and integrations including Salesforce, HooYu and Equifax. Its one of the reasons I've been so excited about the release of bidirectional contract testing. Originally I thought it'd be a case of curling an endpoint to get a public facing version of an Open API spec... until I actually saw the inside of the APIs (SF especially). Am I right in thinking that the base concept for the provider side spec is just "get an OAS in any way you can" and push it to Pactflow, for which Postman-to-oas seems the most sensible call as this is a tool we already use. Do you then need to centre the postman collection on all endpoints and functionality? Or just the bits the consumer cares about (e.g. were not going to use all of Salesforce functionality for our application)

Would you be interested in beta testing the new

publish-provider-contract

method in the Pact CLI for Bi-Directional Contract Testing. It will simplify the existing direct API calls suggested here https://docs.pactflow.io/docs/bi-directional-contract-testing/contracts/oas/#publishing-the-provider-contract--results-to-pactflow If so, just drop me a reaction to this 📫 or a reply in a 🧵

Hi Pactflow team, wanted to ask if there was a release of some new version of Pactflow yesterday or today? We are on Pactflow Version

a48afdec7

currnently, and bi-directional contract verification started failing suddenly without any obvious reason on our side (or I haven’t found it yet). So, I wanted to double-check if this is on Pactflow side. Thanks!

Hello team, I am seeing this error while running provider verification tests - though this does not affect the test run, I was just wondering if I should be concerned? Please advise. Thanks.

❓ time A topic we love to hate, but we have to use. 3rd Party API’s It is listed in our BDCT use cases https://docs.pactflow.io/docs/bi-directional-contract-testing/#use-cases For Consumer-driven Contract testing we’ve said the following and the reasons is expanded on here

Pact is not ideally suited to 3rd party APIs because 3rd parties are unlikely to validate your Pacts

For Bi-Directional Contract testing we said it can help

By pulling in the third party’s API specification (OAS) regularly, you can continually ensure your consumers are compatible

But we are light on examples! What common public API integrations would you like to see an example of? If you have an OpenAPI spec of a public API, feel free to share. If you want to get involved and showcase to a load of 👀 ’s and demo your own example, let your devo 🥑 set the stage for you. Even if you don’t have an answer to the above, but want to see some 🍖 on the 🦴 , then just drop us some kind of emoji. Drop us a reply in a 🧵

We recently started using pactflow tool for contract testing. I see in pactflow we can create different teams. But while publishing pacts to pactflow how to set the 'team name' or use team uuid ? we are using pact CLI to publish pacts. we are using the below pact CLI cmd to publish pacts. I see there is no supported arguments for in 'publish' command to set team-uuid. We use --team-uuid when using 'create-webhook' command, looking for something similar for 'publish' command

docker run --rm -v ${PWD}:${PWD}
pactfoundation/pact-cli publish ${{ pact_folder_path }}
--consumer-app-version ${{ git_commit_version }}
--tag ${{ git_branch }}
--broker-base-url ${{ pact_broker_url }}
--broker-token ${{ pact_broker_token }}

HI there, quick questions regarding BDCT graphql, I know supporting graphql schema is on a roadmap, but is there any way I can use quick BDCT POC for graphql? What is the best strategies for the provider side? convert graphql schema to openapi doc? , btw our provider is REST api but wrapped in graphql mesh, and consumer is graphql. thanks 🙂

Hi! It would be really cool to be able to quickly glance at the number of interactions for each version of a Pact, and maybe even number of failing interactions.

Is there an example of CI/CD using jvm? Would need some help how to pass tags/environments/consumer app version/provider version from gradle when doing provider /consumer test.

Can i clarify the interactions for a consumer/provider CI/CD process. In the first PR for consumer would it always fail because the provider is not verified? The other question i have is about the purpose of webhooks for pactflow. How should i use them in the process? In my head im thinking First consumer PR run 1. Run the consumer pact tests 2. Publish to pact 3. Run can i deploy? (will fail because provider is not verified) but conversely if i try to deploy provider first without consumer run it will also fail because 1. Run the provider pact tests (nothing in broker cause consumer is not run and step will fail) So should it be ? 1. Run consumer pipeline (fail because provider not verified) 2. Run provider pipeline (pass) 3. Rerun consumer again and make it pass • Process seems quite lengthy and easy to "block" each other Please advice

Hello, does pactflow provide mechanism for backups? sorry if it is somewhere, I couldnt information on this.

also I submitted form Pactflow Contract Testing Report - 2021. but did not get any response yet, should I wait for response, or is it possible to get this report any other way?

Hi team - Is there any place where we can check the broker version in Pactflow? So people checking pages like this can confirm which features are available at the moment.

Hi team, whom should I contact about renewing my company's Pactflow subscription?

Not sure if this is the correct channel for this question....I am a pactflow user and want to demonstrate stub server with pactflow....however I have been pushing my teams to use pact spec v3 or v4 and I notice this doc says only spec versions 1.* and 2 are supported. Is there a compelling reason I should/shouldn't want to use the latest spec versions vs. the benefits of stub server?

Hi team! I found that the CI/CD role is missing the

webhook:manage:team

permission. It would be handy to have it added so that teams can configure their webhooks as code and deploy them using system accounts. Thoughts?

hello, any pointers on how to analyze a pactflow broker message for the provider contract "source sequence is illegal/malformed utf-8" with a error reference code