You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,16 +19,17 @@ To simplify the onboarding tutorial, we have created `workshop/pactflow` branch
19
19
This is the second part of the onboarding tutorial. We will verify a published contract in [public tenant](https://test.pactflow.io) on PactFlow. To be able to do it from local environment, you will need to export the following environment variables into your shell:
20
20
21
21
*`PACT_BROKER_TOKEN`: a valid [API token](https://docs.pactflow.io/#configuring-your-api-token) for PactFlow
22
-
*`PACT_BROKER_BASE_URL`: a fully qualified domain name with protocol of public tenant on PactFlow`https://test.pactflow.io`
22
+
*`PACT_URL`: a fully qualified domain name with protocol of public tenant `https://test.pactflow.io`
23
23
24
24
Alternatively, you can create a `.env` file at the project root folder and put the 2 variables in. ie:
Once you have the environment variables setup, you can verify the contract using the following npm command
30
+
Please note it's `PACT_URL`, not `PACT_BROKER_BASE_URL` as specified in [example-consumer](https://github.com/pactflow/example-consumer/tree/workshop/pactflow). Although they are refering to the same thing.
31
31
32
+
Once you have the environment variables setup, you can verify the contract using the following npm command
0 commit comments