-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verifier CLI: configure provider from environment variables #419
Comments
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 |
mjpieters
added a commit
to mjpieters/pact-reference
that referenced
this issue
May 16, 2024
This covers options most often used in CI environments, and should make configuration of the verifier easier using just environment variables. Fixes pact-foundation#419
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: