Closed mjpieters closed 1 month ago
That is easily do-able
here the envs are read in for the token, password or username
would you be up for a PR.
Yup, I can put up a PR for this. I'll model them on the Ruby verifier.
awesome! thank you very much
Currently, the verifier CLI takes the provider configuration from CLI switches:
We have a docker-compose setup with the (instrumented) provider running in a container, and want to use the
pactfoundation/pact-ref-verifier
docker container to run the verification. Ideally, the pact broker configuration for this setup would come from environment variables, so I can just specify these in the docker-compose service.E.g. the docker-compose could look like this:
The advantage is that this configuration now lives right next to the provider configuration that dictates these settings.