Hi team, recently publishing contract for one of p...
# pactflow
w
Hi team, recently publishing contract for one of providers in our org started throwing error. It worked correctly Jul 16th, but 17th it started failing. The error :
[{"detail":"contract content is not a valid OAS document: property '/components/securitySchemes/clientAuth/flows/clientCredentials/tokenUrl' does not match format: uri","pointer":"#/contract/content"},
I compared current version and the last passing one, but it didn't change recently. Can you please advise?
j
Hi Wojciech blobwave We have recently enabled validation of OpenAPI documents on upload, to ensure that any errors in the document are caught early rather than at the time of the bidirectional contract testing. In this case, it seems like you have an invalid internal reference in your OAD.
thankyou 1
The validation of OpenAPI documents on upload was enabled late last week, hence why the 16th upload worked fine, but it then failed validation on the 17th. I believe comms should have gone out? But I can double check if need be.
m
Thanks Josh. Yes we sent out comms in June about this to the account holders. Were you able to update the definition OK? Whilst we understand it’s a bit of a pain, in reality downstream problems were likely to happen during comparison/rendering (or already happening) and this was just masking the problem.