Any plans for supporting OpenAPI v3.1 in the future?

Hi Team, I am doing my first bidirectional contract test. But at contract verification fails with following error

Request Header Is Incompatible Value is incompatible with the parameter defined in the spec file: should have required property 'value' Mismatched Pact Path: [root].interactions[0] Mismatched Provider Path: [root].paths./**.post.parameters[0]

but there is no such property 'value' in either provider side or consumer side\

Hi team! The documentation for the admin endpoints is missing in the HAL browser. Does anyone know where to find that, or if that's something that will be available at some point? I'd like to do simple things like listing all the active system accounts (the UI doesn't allow filtering at the moment) and similar operations. Thanks!

Hi! This might be a silly idea, but considering that the Open Api spec allows including "examples" (At least through Swagger), have you considered allowing using these for provider stubs? Could be useful for bi-directional testing.

Hey there! I'm getting the following error:

There is no verified pact between version 1.0.0 of demo-app and a version of GameService currently deployed or released to production (no version is currently recorded as deployed/released in this environment)

when running can-i-deploy. How do I configure/set the environment for my consumer + provider contracts? I couldn't find it in the Pact Broker Client CLI commands.

Hi, I have just started using Pact. I created a free starter account here -https://pactflow.io/try-for-free/?utm_source=homepage&utm_content=hero . Successfully received email with credentials and url to Pactflow account. I could also log into it and see default example set up . But now I am trying to connect to the same account and it gives me error , the url is not reachable

For BDCT, we're having some trouble figuring out this error.

Response body is incompatible with the response body schema in the spec file: should NOT have additional properties - id
Mismatched Pact Path:
[root].interactions[0].response.body.paymentMethods[0]
Mismatched Provider Path:
[root].paths./userprofile/v1/paymentmethods.get.responses.200.content.application/json.schema.properties.paymentMethods.items.additionalProperties

In our provider contract, if we follow the provider path, items can be

anyOf

, as seen below

responses:
        '200':
          description: Successful response
          content:
            application/json: 
              schema:
                type: object
                properties:
                  paymentMethods:
                    type: array
                    items:
                      anyOf:
                        - $ref: '#/components/schemas/creditCard'
                        - $ref: '#/components/schemas/bankAccount'

 schemas:
    creditCard:
      type: object
      properties:
        id:
          type: integer
        userId:
          type: integer
        externalId:
          type: string
        type:
          type: string
        lastFour:
          type: string
        isPrimary:
          type: boolean
        issuer:
          type: string
        verificationStatus:
          type: string
        expiration:
          type: object
          properties:
            year:
              type: integer
            month:
              type: integer

We're wondering why the contract comparison can't find the schema definition?

paymentMethods[0]

is matching the credit card schema currently in our consumer contract As an aside, should BDCT questions be in #C5F4KFKR8 or #CLS16AVEE (since it's currently just a pactflow feature)?

Might be a stupid question but I've had a look around the docs and couldn't find anything. What are the options around configuring multiple brokers for consumers? (an existing pact broker and a newer pactflow instance) Or is there a way to transition to pactflow while keeping the history of verifications etc?

is it just me or is the verifier paramter in the publish-provider-contract command not really doing a lot?

Hello! Trying to migrate from gitlab ci to github actions. I used https://github.com/pactflow/example-bi-directional-provider-dredd as a reference (Thank you Pactflow team for that). Sending the provider contract works on local machine but is failing on github with strange error:

NoMethodError - undefined method `request_uri' for #<URI::Generic ?>

Hi everyone! All examples on github have

.env

target in the pact related actions: https://github.com/pactflow/example-bi-directional-provider-dredd/blob/master/Makefile#L34 For me it doesn't expose variables from the existing

.env

file on macos. So I ended up adding the snippet on the top of Makefile:

# Export all variable to sub-make if .env exists
ifneq (,$(wildcard ./.env))
    include .env
    export
endif

Am I doing it wrong way?

Hi, all. I post here this article that we wrote in our company. Hope helps!

Any feedback is welcome 😁

The Matrix tab on pactflow UI isn't displaying accurate verification statuses for me. "Can I deploy" and cross-contract-verification-result pages in the UI do give the correct result however. It's happening fairly frequently so wasn't just a one off. I've tried the refresh button but it doesn't change. Should they not just be displaying the same status?

Hello, I have just signed up for pactflow and created an account. Now I would like to publish the pact file generated by the consumer to my pactflow account. I have the authentication token with me. My question is how to publish the pact file to pactflow.io on Windows/.Net core. I have seen this example, however this is not working. any ideas on this?

$Headers = @{

Authorization = "Basic $([System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes("dXfltyFMgNOFZAxr8io9wJ37iUpY42M:O5AIZWxelWbLvqMd8PkAVycBJh2Psyg1")))" } $res = Invoke-WebRequest -Uri "https://test.pactflow.io/pacts/provider/Animal%20Profile%20Service/consumer/Matching%20Service/version/1.0.0" -Headers $Headers -Method Put -InFile .\matching_service-animal_profile_service.json -ContentType "application/json"

Hi, we are trying to setup a new provider for pact flow but when running the pact.verify() we get this error

Error retrieving <https://cinch.pactflow.io/pacts/provider/marketplace-gateway-component/for-verification> status=404  (Pact::Hal::ErrorResponseReturned)

question regarding using pactflow(hosted broker), is there any disadvantage to use both BDCT and CDCT ? and store pacts in pactflow? if team, use REST services( both provider and consumer) AWS lambda + API gateway=REST and they want to use BDCT, and the other services (graphql) uses CDCT, is there any issue to mix both contract way? no right? because each pacts are mapping separately and only concern their contracted services each other. so people can select whatever they want to use?

Hi - Our OAS has a lot of allOfs , oneOfs and we are getting false failures while doing BDCT. Is there a quick setting on the pact side to make "additionalProperties":true - rather than adding it on multiple times on schema? Requesting help here.

Hi all, I am verifying a pact on pactflow and it shows that it is verified in terminal but once I go to pactflow it still shows unverified. Is there a command I need to run to get it to ber verified in pactlfow. I am simply just running yarn test for now.

Getting started with bi-directional contract testing....

Hi team, I already have a OAS and wanna publish it to pactflow. I’m wondering why it will give me this error?

./pact/bin/pactflow publish-provider-contract ./openapi.yaml  --provider=CC-Go-Template-Service-Provider -a v0.01 --broker-base-url=<https://mydns.pactflow.io> -k $PACT_TOKEN --branch main --contentType=application/yaml --verification-exit-code=0

ERROR: "pactflow publish_provider_contract" was called with arguments ["./openapi.yaml", "--contentType", "application/yaml"]

Usage: "pactflow publish-provider-contract CONTRACT_FILE ... --provider=PROVIDER -a, --provider-app-version=PROVIDER_APP_VERSION -b, --broker-base-url=BROKER_BASE_URL"

PS: I’ve read the publish-provider-contract page and its repo, I’m wondering if it’s necessary to have the collection first and run the newman in CI then publish?

Hi all, is there full compatibility for ci/cd integration with both pact and pactflow? What would be the main differences for ci/cd when using pactflow vs when using just pact and having you own broker.

Hi all! We are looking at BDCT using Pactflow. I'd love a sanity check on some of my thinking on the practical workflow. Say a developer on a Provider team makes a deliberate breaking change to an endpoint and updates the OAS accordingly. The API tests would have to be updated at the same time to ensure the contract which will be generated from the OAS matches the change being made to the endpoint. To allow a test specialist to update the API tests, would you then have the developer and test specialist make their changes on the same branch (whether it be async or in a pair programming session)? How are others doing this? Also, say the Consumer is ready with an update to match the change on the Provider side. The Provider isn't able to merge their change yet, because they're breaking a Consumer. Because of this, the Consumer also isn't able to merge their change, because the Provider doesn't meet their new expectations yet. Is this resolved by the Provider and Consumer using identically named branches in their respective repos so that the contracts can be tagged and verified against their working branches? Or is this where the WIP Pacts feature would tell the Consumer that they get a fail for the main branch but they may get a pass from the WIP pacts which includes the new Provider one and which will unblock that Provider? confused dog 2741

Hi team, is it possible to create/disable/delete users using the REST API endpoint

admin/users

in Pactflow? If yes, where can I find the documentation? I'm trying to build some kind of user onboarding automation, and the built-in HAL Browser isn't very useful IMHO.

question about Hosted API Stubs, this seems like a really useful feature as described in the blog post, eg starting your react app with the consumer pact stubs. however, how would one handle the case where a consumer (let's say react web app), has many providers? it looks like the api support in pactflow supports a stub endpont of 1:1 , provider:consumer. when really i want All Providers for a given consumer.

Hi Team 👋 . I’m having some issues with a new Webhook that does not seem to be Authorising with the GitHub url i am trying to trigger. Testing the trigger always returns a 404 from GitHub. We have other webhooks (all still working) that use the same auth token (stored in Secrets) and I can also trigger the GitHub repo using a simple curl request from my Terminal. I have also regenerated our GitHub Auth Token, just to see if that could help. Happy to provide links to our webhooks on pactflow, if you think it will help. Thanks

Hi all! 👋 Does bi-directional testing support anything similar to pending states? Im trying to add bi-directional testing to my pipeline, I want consumer's pull requests to be checked against the latest provider version, but I don't want those checks to fail if they're hitting endpoints which hasn't been published yet in our provider. Also, where do we bind consumers with providers in a bi-directional workflow? Can a consumer have multiple providers? Would this require having a pact for each provider? Thank you for your work btw, Pact is amazing 💪!