From edf629b58bf62591338e331c0ab622ea6d2c3549 Mon Sep 17 00:00:00 2001 From: Riccardo Solazzi <129967922+TheZalRevolt@users.noreply.github.com> Date: Thu, 28 Dec 2023 12:48:19 +0100 Subject: [PATCH] Update policy-repo-syncing.mdx --- .../running-opal/run-opal-server/policy-repo-syncing.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/documentation/docs/getting-started/running-opal/run-opal-server/policy-repo-syncing.mdx b/documentation/docs/getting-started/running-opal/run-opal-server/policy-repo-syncing.mdx index 60c6e008c..f2e0d0a3c 100644 --- a/documentation/docs/getting-started/running-opal/run-opal-server/policy-repo-syncing.mdx +++ b/documentation/docs/getting-started/running-opal/run-opal-server/policy-repo-syncing.mdx @@ -25,6 +25,8 @@ It is much more recommended to use webhooks if your policy repo is stored in a s If your server is hosted at `https://opal.yourdomain.com` the webhook URL you must setup with your webhook provider (e.g: github) is `https://opal.yourdomain.com/webhook`. See [GitHub's guide on configuring webhooks](https://docs.github.com/en/developers/webhooks-and-events/creating-webhooks). +Keep in mind that the webhook should be in `JSON` format. + Typically you would need to share a secret with your webhook provider (authenticating incoming webhooks). You can use the OPAL CLI to create a cryptographically strong secret to use. Let's install the cli to a new python virtualenv:{" "}