Hello All :wave: I got a problem with pact broker...
# pact-broker
f
Hello All đź‘‹ I got a problem with pact broker We have a list of pacts for a provider to be verified, the name of the provider is 'application-versioning-service' and the consumer service is 'publish-service' The pactnet nugget attempts to retrieve the contract to be verified by using the following call:
Copy code
[10h26] 2022-08-31T07:31:01.8906579Z [DEBUG][pact_verifier::pact_broker] Sending JSON to <https://outsystems.pactflow.io/pacts/provider/application-versioning-service/for-verification> using POST: {"providerVersionTags":[],"includePendingStatus":true,"consumerVersionSelectors":[{"consumer":"publish-service","mainBranch":true}]}
For any other consumer it is working fine, we get the specific contract but for that one - 'publish-service' he doesn't give anything and it returns that pact couldn't find the contract. When i checked out using the API browser using the following call (for the contracts to be verified endpoint that the url use)
Copy code
{
  "providerVersionTags": [],
  "includePendingStatus": true,
  "consumerVersionSelectors": [
    {
      "consumer": "publish-service",
      "mainBranch": true
    }
  ]
}
i got the response where i got all contracts (but no publish-service one) when
"consumer"
is, for example, another one (like alm-app) i get only that one (as expected)
b
Hi @Fábio Rodrigues. Can you share the pacticipant resource for the publish-service please.
It will be at
/pacticipants/publish-service
]
f
Sem_titulo.json
message has been deleted
b
The pacticipant looks fine. And because it’s in Pactflow, I can actually have a look at it for you.
@Fábio Rodrigues can you send a request to support@pactflow.io so I can look into this for you?
I wonder if it’s related to the issue that @Édouard Lopez has found.
f
i think it is the same issue about the pact for verification