Closed NigelVanHattum closed 3 years ago
Unrelated, you don't need both the pact URL and the Pact Broker URL. Have a look at the "Description" section in the Usage https://github.com/pact-foundation/pact-provider-verifier#usage
If it's a 503, that's a server error. Probably not something wrong with your client code, unless you're pointing the Pact Broker URL to the wrong location. Can you access the Pact Broker through the UI? Can you put the --verbose flag on to make sure you're actually getting that 503 from the Pact Broker itself? A 503 is likely to come from a reverse proxy or something sitting in between your client and the Pact Broker application like a load balancer or ngnix, not the Ruby code itself.
It seems to be a proxy issue indeed. A reverse proxy shoudn't be an easy I guess?
It seems to be a proxy issue indeed. A reverse proxy shoudn't be an easy I guess?
I don't understand the question sorry, are you asking if setting up a reverse proxy should be easy?
We are trying to setup our pipelines to validate PACTs for our consumers. We've got a PACT broker setup which stores the contracts.
We are trying to validate them with the following command:
This results in the following stack trace:
We are able to connect to both the PACT broker and the provider via the same pipeline.