https://pact.io logo
Join Slack
Powered by
Is there a required workflow order needed in order...
# pactflow
j
Is there a required workflow order needed in order to tell the broker that contracts should exist? I'm attempting to spin up some provider tests but 
pact-provider-verifier
keeps returning with something similar to the following: (organization and project have been masked)
Copy code
/usr/lib/ruby/gems/3.1.0/gems/pact-1.63.0/lib/pact/hal/entity.rb:102:in 'assert_success!': Error retrieving https://${organization}.<http://pactflow.io/pacts/provider/${project}-provider-golang/for-verification|pactflow.io/pacts/provider/${project}-provider-golang/for-verification> status=404 {"error":"The requested document was not found on this server."} (Pact::hal::ErrorResponseReturned)
b
Does the provider exist in your Pactflow account?
j
does this need to be created manually?
m
can you please share a bit more to help us diagnose what’s going on here? e.g. have you published your contract? What arguments are you passing to the CLI?
b
Are there any pacts published for the provider?
Generally, you’d publish a consumer contract first.
That will create the provider resource.
This workshop explains the process https://docs.pactflow.io/docs/workshops/ci-cd
j
thank you! I'll look at that.
For Matt's concerns, it would appear that I have NOT published a contract yet since I started with the provider rather than the consumer. That'll be my next step.
👍 1
after reading the workshop docs that is
As far as CLI goes, I'm using the golang testing tools (
go test ./...
) with environment variables to configure the 
VerifyRequest
object used by 
VerifyProvider
m
Right. Pact is a consumer driven tool, so usually best to start with the consumer. You can do provider first of course, but you won’t have anything to validate
7 Views
Open in Slack
PreviousNext
Powered by