Hey guys, I am new to PACT/Pactflow, I am currentl...
# pact-python
t
Hey guys, I am new to PACT/Pactflow, I am currently building a bi-directional contract testing POC. Our consumer is in typescript and the provider is a python based service. So far, I was able to publish my consumer contract to pactflow and I also used the pact standalone cli to publish the openapi spec to pactflow from the provider:
Copy code
./pact/bin/pactflow publish-provider-contract \
  "openapi/v0/openapi.yaml" \
  --broker-token=<token> \
  --broker-base-url=<https://adae.pactflow.io> \
  --specification=oas \
  --provider "messaging-api" \
  --provider-app-version 12345\
  --branch cdc \
After I ran the above, it published the openapi spec and also validated the consumer contract but I also noticed the provider contract (self verification) was not done. That's the piece I am a bit confused about. Our openapi spec is manually generated and we use pytest to validate it. How can I get the provider contract (openapi) to be validated in pactflow as well? I saw the below args for the CLI but I am not quite sure how to use them. --verification-exit-code=EXIT_CODE \ --verification-results REPORT_PATH \ --verification-results-content-type REPORT_CONTENT_TYPE \ --verifier VERIFIER Is it even necessary to do the provider contract self validation in pactflow if we already have tests that validate the openapi spec? I am also contemplating using dredd maybe to validate our openapi spec. I am looking for a bit of guidance, best practice etc. Any help is greatly appreciated.