Configure webhook
When using Pact in a CI/CD pipeline, there are two reasons for a pact verification task to take place:
When the provider changes (to make sure it does not break any existing consumer expectations)
When a pact changes (to see if the provider is compatible with the new expectations)
To ensure that the verification step is run whenever a pact changes, we need to configure a PactFlow webhook to trigger a provider verification build in Github Actions. You can see the configuration for this build in .github/workflows/verify_changed_pact.yml
in the provider project. Rather than verifying the pacts with the configured tags, this build just verifies the pact that has changed. This is achieved by passing the URL of the changed pact to the build via a parameter in the body of the webhook request.
The PactFlow webhook will need a Github access token to be able to trigger the build in Github. We don't want the Github token to be stored in clear text in the webhook, so we will create a secret in API Hub for Contract Testing to contain token.
Create a Github token.
Open the
Personal access tokens page
Click on your profile picture in the top right of the window.
Select
Settings
-> SelectDeveloper settings
from the bottom of the menu on the left -> SelectPersonal access tokens
from the menu on the left.
Click
Generate new token
Set
Note
toToken for triggering example-provider pact verification build
Select
public_repo
scope.Click
Generate token
Copy the value of the token and put it in an open file (or better yet, store it in your password manager!)
Create a API Hub for Contract Testing secret to the Github token.
In your API Hub for Contract Testing account:
Go to the Secrets page
Click on the Settings icon in the top left (it looks like a cog wheel) -> Select the
Secrets
tab from the menu on the left.
Click "ADD SECRET"
Select "None" in the team drop-down box.
Enter the name
githubToken
and paste the value that you copied in the previous step.Click "CREATE"
Create the webhook.
In your API Hub for Contract Testing account:
Select the
Webhooks
tab from the settings page.Click "ADD WEBHOOK".
Set:
Team: None
Description:
Pact changed webhook for pactflow-example-provider
Consumer: leave as "ALL"
Provider: select
pactflow-example-provider
Events: select
Contract published with changed content or tags
URL:
https://api.github.com/repos/<YOUR GITHUB ACCOUNT HERE>/example-provider/dispatches
Headers:
Content-Type: application/json Accept: Accept: application/vnd.github.everest-preview+json Authorization: Bearer ${user.githubToken}
Body:
{ "event_type": "pact_changed", "client_payload": { "pact_url": "${pactbroker.pactUrl}" } }
Click the "TEST" button and ensure that it runs successfully.
👉 The Github API returns a 404 instead of an authorization error if the token is not correctly set. If you see a 404, it may be that the URL is incorrect, or it may be that the access token is not configured correctly.
Click the "CREATE" button.
Verify that the pact verification build for the provider is running correctly
In Github:
Open the Github Actions page for the "Verify changed pact" workflow
Click
Actions
-> UnderWorkflows
, selectVerify changed pact
Select the latest execution
👉 Each of the above steps can be automated in API Hub for Contract Testing via the API Hub for Contract Testing API - you can see the targets for the commands in the provider's Makefile.
Expected state by the end of this step
Both consumer and provider builds passing ✅
A webhook that has been tested and shown to trigger a pact verification build of the provider.