https://pact.io logo
Join Slack
Powered by
# pactflow
  • d
    Hi All, I'm trying to publish a provider using 
    pactfoundation/pact-cli:latest
    docker image. There I can get only 
    pact-provider-verifier
    . But I want to publish the provider contract similarly how it get publish by 
    pactflow publish-provider-contract
    by using the standalone pact cli. Anyone please help me. Thanks
    👋 1
    a
    m
    y
    • 4
    • 17
  • k
    HI All, I am trying to setup bi-directional testing using my existing pact-server without using pactflow. is it feasible? This is for an in-house experiment. I am publishing different fragments from the producer and consumers also producing their subset to the pact broker. And I need a way of identifying all the consumer published pacts from provider., which is what I believe PACTflow with bi-directional contract testing is doing.. Sorry for any incorrect understanding..
    m
    y
    +2
    • 5
    • 7
  • r
    Hi pactflow channel. With bi-directional contract testing, is it possible to define the request path for the consumer contract in a case insensitive way OR to configure the pactflow broker to use a case insensitive compare between the consumer contract path and the open api schema path? Our providers are primarily .net apps which use case insensitive routing out of the box and our open api schema specs are generated from the code using swashbuckle which outputs the swagger.json spec using pascal cased paths for the operations. This is causing pact verification failures due to case differences in the paths that don't matter for our apis.
    y
    m
    • 3
    • 14
  • w
    Does the support@pactflow.io email have filters that prevent messages from being sent? I've been trying to submit a ticket for an issue we're seeing in our pactflow instance, but my email keeps getting bounced as spam
    y
    • 2
    • 1
  • t
    Has anyone seen this issue with Pactflow Login when trying to sign in with SAML? 
    Error logging in. invalid_ticket. Error reference: tGSLqEmNbU
    y
    b
    • 3
    • 11
  • n
    Hey all, does anyone know how to add multiple pact tests to a consumer as well a provider? Meaning, if a provider services several different consumers how would that look like? And if a consumer has several different providers how would that look like?
    h
    m
    • 3
    • 9
  • w
    Has anyone run into an issue with Pactflow where in Pactflow, the contract compatibility returns ✅ , but can-i-deploy fails? I get the generic failure message, but on verbose, it says verificationStatus failed. Clicking the link to the failure though brings me to the Pactflow verification results, that say it passed. The matrix view also shows no failures. Strangely though, no contract changes have been made either. Just randomly blocking our pipeline starting today
    h
    m
    +2
    • 5
    • 9
  • e
    Hey, Is there any way using the Pactbroker CLI to exchange the long-lived bearer token for a short-lived access token?
    m
    • 2
    • 5
  • a
    Hello, we're currently attempting to validate a bi-directional contract using can-I-deploy. The problem we're running into is a mismatch between what PactFlow is showing, and what the can-I-deploy tool is returning. Using the same versions and tags on both pacticipants, PactFlow shows the consumer and provider OAS contracts are compatible with one another. However, when running the can-I-deploy, which is part of the CICD process when merging consumer from feature branch to main branch, can-I-deploy returns false. Even when we follow the link that shows the failed interaction that is displayed in the response of can-I-deploy, we see that the contracts pass and are compatible with each other. We attempted deleting consumer contract, and restarting the process, but we run into the issue with the can-I-deploy failing which is preventing us from being able to merge to main (without modifying the pipeline). Any advice on where to go from here?
    b
    m
    • 3
    • 17
  • j
    Hi all .. Thank you very much in advance for the help. We are having the following situation: Consumers are correctly publishing contracts to pactflow, since the content of the contract has not changed we expect the contract to be marked as verified by the provider which is already deployed to a given environment. But, this is not the case, the contract shows as not verified at all. Any ideas?
    👋 1
    m
    b
    • 3
    • 12
  • s
    Hi I created a project from create sample project from pactflow for bidirectional and getting errors on npm test gem bundler ruby gems loader molinillo etc
    m
    s
    • 3
    • 3
  • s
    Logged into pactflow account
  • s
    Created a sample project with bidirectional provider javascript node provider mocha as template
  • s
    Open downloded folder in vscode
  • s
    Npm install Npm test
    m
    y
    • 3
    • 11
  • j
    Hi! I got another doubt .. we have a service which is provider and consumer ... when we request can-i-deploy through the api: https://pactflow.xxx.io/can-i-deploy?pacticipant=yyyyyy&version=zzzzzzz&environment=dev The response is true ... all good, we are happy ... but when we do the verification with pact-broker command line tool from Jenkins it says no ...
    Copy code
    pact-broker can-i-deploy --pacticipant=yyyyy--broker-base-url=<https://pactflow.xxxx.io> --broker-token=**** --version=zzzzzzzz --to-envionrment=dev
    Copy code
    CONSUMER              | C.VERSION  | PROVIDER              | P.VERSION  | SUCCESS? | RESULT#
----------------------|------------|-----------------------|------------|----------|--------
wwwwwwwwwwwwwwwwwwww  | e22e444... | yyyyyyyyyyyyyyyyyyyyy | b5b0a6c... | true     | 1      
yyyyyyyy              | b5b0a6c... | kkkkkkkkkkkkkkk       | ???        | ???      |
    Any ideas what could we be missing? Thanks a lot in advance, much appreciated the help. Regards!
    b
    • 2
    • 1
  • b
    It seems like the current docker image for pact-cli is broken?
  • b
    Copy code
    [2022-12-01T16:11:52.816Z] Error retrieving matrix. PactBroker::Client::Hal::ErrorResponseReturned - Error making request to <https://hmhco.pactflow.io//matrix> status=404
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/hal/entity.rb:197:in `assert_success!'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/hal/link.rb:45:in `get!'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/matrix/query.rb:11:in `call'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/base_command.rb:13:in `call'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/can_i_deploy.rb:107:in `block in fetch_matrix'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/retry.rb:22:in `while_error'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/can_i_deploy.rb:107:in `fetch_matrix'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/can_i_deploy.rb:111:in `fetch_matrix_with_retries'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/can_i_deploy.rb:34:in `call'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/can_i_deploy.rb:23:in `call'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/cli/matrix_commands.rb:36:in `can_i_deploy'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/base.rb:485:in `start'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/pact_broker-client-1.66.0/lib/pact_broker/client/cli/custom_thor.rb:23:in `start'
[2022-12-01T16:11:52.834Z] /pact/lib/pact/cli.rb:46:in `broker'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/thor-1.2.1/lib/thor/base.rb:485:in `start'
[2022-12-01T16:11:52.834Z] /pact/bin/pact:15:in `<top (required)>'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/lib/bundler/cli/exec.rb:58:in `load'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/lib/bundler/cli/exec.rb:58:in `kernel_load'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/lib/bundler/cli/exec.rb:23:in `run'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/lib/bundler/cli.rb:483:in `exec'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/lib/bundler/cli.rb:31:in `dispatch'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/lib/bundler/cli.rb:25:in `start'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/exe/bundle:48:in `block in <top (required)>'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/lib/bundler/friendly_errors.rb:103:in `with_friendly_errors'
[2022-12-01T16:11:52.834Z] /usr/lib/ruby/gems/3.0.0/gems/bundler-2.3.13/exe/bundle:36:in `<top (required)>'
[2022-12-01T16:11:52.834Z] /usr/bin/bundle:25:in `load'
[2022-12-01T16:11:52.834Z] /usr/bin/bundle:25:in `<main>'
    b
    m
    d
    • 4
    • 20
  • b
    seems like it's just 0.51.0.0 that is busted
  • b
    0.50.0.32 works
  • w
    Hello, is there an API endpoint available to delete 'the integration'? I found the piece of documentation where it states how to do it with the GUI and I wondered whether it may also be available using the API.
    m
    y
    • 3
    • 4
  • c
    Hello, I have a swagger.json and a pact file (see attachments). If I publish them to Pactflow, I get the following strange error (see attached screenshot): Validator Error Cannot read properties of undefined (reading 'type') This error does not seem to be one of those "Contract Incompatibility Messages", which are listed here: https://docs.pactflow.io/docs/user-interface/bi-directional/ Could it be that this might point to an exception thrown inside the Pactflow? Is something wrong with one or both of my files which causes Pactflow to throw an exception or something? To reproduce the error, just publish both of the files to Pactflow server.
    MailClient-MailAPI.jsonswagger.json
    b
    m
    • 3
    • 5
  • k
    Hi team, we (vodafone) have sent email to security@pactflow.io in October 2022 for security assessment for pact flow and we didn't hear back on it. Could you please share right contact to follow up with it?
    m
    • 2
    • 4
  • s
    What it means unknown status in pactflow though pact are compatible in bidirectional
    m
    • 2
    • 27
  • s
    ?
  • s
    Github actions and workflow configuration not displaying for my private repositories
    m
    y
    • 3
    • 4
  • n
    Hey team! Just to confirm.... we have a consumer which is an iOS application where we can't apply bi-dirctional contract testing because none of supported tools are being used, and then we have a provider where we can apply bi-directional feature because Postman and SwaggerHub are used. So is it compatible to apply bi-directional feature in the provider side with a non-bi-directional (iOS app) in the consumer side? thanks in advance
    👋 1
    y
    m
    • 3
    • 4
  • j
    Bi-directional verification Hi folks, I am trying to implement a bi-directional verification, but I am cracking my head with an error message regarding the path. Apparently the consumer contract and the Swagger spec are specify the same API method: POST /executeFlow/orderlookup/V1 But Pactflow says the paths are incompatible. Any thoughts? Note: The Swagger spec provided to me has a mismatch on the response body - this I know. I am confused about the error on the paths.
    y
    m
    • 3
    • 11
  • s
    How to create pact files if i have 100+ requests, do I have to create 100 pact files?
    m
    t
    • 3
    • 8
  • s
    What is reciprocal. json does in postman provider?
    m
    b
    • 3
    • 6
1...678...13Latest