https://pact.io logo
Join Slack
Powered by
Hello, I have a question regarding the content of ...
# pact-broker
e
Hello, I have a question regarding the content of the body that I can send in the URL of 
pb:publish-verification-results
. I see in the documentation that the body to be sent is this:
Copy code
{
  "success": true,
  "providerApplicationVersion": "1.0.1",
  "buildUrl": "<http://my-ci.org/build/3456>"
}
Is it possible to send the following variables
Copy code
{
  "success": true,
  "providerApplicationVersion": "1.0.1",
  "providerVersionTags": [
    "development"
  ],
  "branch": "my-branch"
}
so that the Broker can store that information?
m
The discussion here implies that sort of thing, but the payload is not defined clearly there (it could be the right one, but I think it’s more indicative): https://github.com/pact-foundation/pact_broker/discussions/425
We didn’t documented in our API here: https://smartbear.portal.swaggerhub.com/pactflow/default/getting-started (PactFlow’s APIs are a superset), presumably because it’s not something many people use directly.
May I ask why you’re are using it directly instead of via our tools? Might help us uncover a use case
The simplest way to find out actually, is just run a verification using the Ruby Verifier CLI, and enable 
--verbose
and add all the flags you care about to see what is passed through
e
I’m implementing the provider in a Node.js project. The issue is that since the JavaScript library doesn’t support x509 certificates, I have to make 
curl
calls to the broker to communicate the test provider’s results.
m
Do you mean, you need to send an x509 cert with the request e.g MASSL?
👀 1
You could potentially add that capability to the project
Open in Slack
PreviousNext
Powered by