Skip to content

Commit aa91902

Browse files
committed
chore: add verify_pacts task
1 parent b73e378 commit aa91902

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

README.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,16 +19,17 @@ To simplify the onboarding tutorial, we have created `workshop/pactflow` branch
1919
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:
2020

2121
* `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`
2323

2424
Alternatively, you can create a `.env` file at the project root folder and put the 2 variables in. ie:
2525
```
26-
PACT_BROKER_BASE_URL=https://test.pactflow.io
26+
PACT_URL=https://test.pactflow.io
2727
PACT_BROKER_TOKEN=<<whatever-the-token-you-found>>
2828
```
2929

30-
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.
3131

32+
Once you have the environment variables setup, you can verify the contract using the following npm command
3233
```
3334
npm run verify_pacts
3435
```

0 commit comments

Comments
 (0)