Hi, we’re reviewing the Pact bi-directional flow f...
# general
r
Hi, we’re reviewing the Pact bi-directional flow for our company, any idea how we can turn this unknown status?
message has been deleted
message has been deleted
message has been deleted
Is it the “Missing Self Verification Result” that creates this “compatibility status unknown”?
m
Thanks for raising in #CLS16AVEE after (that’s the right place)
Yes, it’s the missing self-verification result
You just need to set the flags on the publish step e.g.
Copy code
...
  --verification-results /path/to/results.txt \
  --verification-results-content-type text/plain  \
  --verifier readyapi \
  --verification-success
Copy code
✗ pactflow help publish-provider-contract
Usage:
  pactflow publish-provider-contract CONTRACT_FILE ... --provider=PROVIDER -a, --provider-app-version=PROVIDER_APP_VERSION -b, --broker-base-url=BROKER_BASE_URL

Options:
      --provider=PROVIDER                                                      # The provider name
  -a, --provider-app-version=PROVIDER_APP_VERSION                              # The provider application version
  -h, [--branch=BRANCH]                                                        # Repository branch of the provider version
  -t, [--tag=TAG]                                                              # Tag name for provider version. Can be specified multiple times.
      [--specification=SPECIFICATION]                                          # The contract specification
                                                                               # Default: oas
      [--content-type=CONTENT_TYPE]                                            # The content type. eg. application/yml
      [--verification-success], [--no-verification-success]                    # Whether or not the self verification passed successfully.
      [--verification-exit-code=N]                                             # The exit code of the verification process. Can be used instead of --verification-success|--no-verification-success for a simpler build script.
      [--verification-results=VERIFICATION_RESULTS]                            # The path to the file containing the output from the verification process
      [--verification-results-content-type=VERIFICATION_RESULTS_CONTENT_TYPE]  # The content type of the verification output eg. text/plain, application/yaml
      [--verification-results-format=VERIFICATION_RESULTS_FORMAT]              # The format of the verification output eg. junit, text
      [--verifier=VERIFIER]                                                    # The tool used to verify the provider contract
      [--verifier-version=VERIFIER_VERSION]                                    # The version of the tool used to verify the provider contract
  -o, [--output=OUTPUT]                                                        # json or text
                                                                               # Default: text
  -b, --broker-base-url=BROKER_BASE_URL                                        # The base URL of the Pact Broker
  -u, [--broker-username=BROKER_USERNAME]                                      # Pact Broker basic auth username
  -p, [--broker-password=BROKER_PASSWORD]                                      # Pact Broker basic auth password
  -k, [--broker-token=BROKER_TOKEN]                                            # Pact Broker bearer token
  -v, [--verbose], [--no-verbose]                                              # Verbose output. Default: false
r
Awesome, I’ll look at that, thank you @Matt (pactflow.io / pact-js / pact-go)
🙌 1