Hi folks, Regarding bi-directional verification, ...
# pactflow
j
Hi folks, Regarding bi-directional verification, where the Contract Verification Status is Compatible (On the "View Contract" page, but in the Overview page I see the integration status as Unknown, not Success as it happens when a consumer-driven integration is verified. When I run can-i-deploy, it says that there is no verification results for this integration. Is this expected? Am I misinterpreting something here?
m
When you publish your provider contract, you must say the verification status to successful
j
Ah, got it. Thanks Matt. Now I am facing another problem. When trying to re-publish the OpenAPI file, I am facing a 404 error "The requested document was not found on this server". Either using the same version or a different verion. I don't get exactly why a 404 if I am trying send data to the server. Any ideas?
m
I think you need to drop the additional trailing
/
on the URL
note how there are two
//
in the URL (if you set
--verbose
on you’d see the request path in more detail).
j
Ah, got it. I was able to upload now. One question Matt: Currently I am dealing with a provider that doesn't have any validation of the OpenAPI spec, like Dredd. So, when I send only --verification-success, I get a "verifier is missing". I see Pactflow will accept even fake report, but I would prefer to not have this in the pipeline. Is it possible to send only --verification-success, with the verifier and the report?
m
It is not sorry. The report can be anything that describes why you think it is correct How do you know it's safe then if you're not testing it
f
when the service itself creates the openapi document from it's code
👍 1