update broker docs to remove publicKey, allowedIps, heartbeat (#1936)

Author: khorne3

docs/semgrep-ci/network-broker.md

@@ -36,6 +36,38 @@ Ensure that you are logged in to the server where you want to run Semgrep Networ
 
 ### Create the config file
 
+<Tabs
+    defaultValue="current"
+    values={[
+    {label: 'v0.25.0 and later', value: 'current'},
+    {label: 'v0.24.0 and earlier', value: 'legacy'}
+    ]}
+>
+
+<TabItem value='current'>
+
+Create a `config.yaml` file similar to the following snippet, or copy a starting config from the Semgrep AppSec Platform at  **Settings > Broker**. The steps required to generate values for the placeholders `SEMGREP_LOCAL_ADDRESS`, `YOUR_PRIVATE_KEY`, and `YOUR_BASE_URL` are provided in subsequent steps of this guide.
+
+```yaml
+  inbound:
+    wireguard:
+      localAddress: SEMGREP_LOCAL_ADDRESS
+      privateKey: YOUR_PRIVATE_KEY
+      peers:
+        - endpoint: wireguard.semgrep.dev:51820
+    allowlist: []
+    gitlab:
+      baseUrl: YOUR_BASE_URL
+      token: GITLAB_PAT
+```
+
+</TabItem>
+<TabItem value='legacy'>
+
+:::note
+Semgrep recommends that users running Network Broker v0.24.0 or earlier to upgrade to v0.25.0 or later. This enables the use of a simplified config file.
+:::
+
 Create a `config.yaml` file similar to the following snippet, or copy a starting config from the Semgrep AppSec Platform at  **Settings > Broker**. The steps required to generate values for the placeholders `SEMGREP_LOCAL_ADDRESS`, `YOUR_PRIVATE_KEY`, and `YOUR_BASE_URL` are provided in subsequent steps of this guide.
 
 ```yaml
@@ -61,6 +93,9 @@ The `publicKey` value should be entered precisely as shown in the example:
 4EqJwDZ8X/qXB5u3Wpo2cxnKlysec93uhRvGWPix0lg=
 ```
 
+</TabItem>
+</Tabs>
+
 #### Multiple configuration files
 You can overlay multiple configuration files on top of each other by passing multiple `-c` arguments:
 
@@ -96,7 +131,7 @@ The broker requires a WireGuard keypair to establish a secure connection. To gen
 
 ### Update the config with your SCM information
 
-Update the `config.yaml` by replacing the SCM information containing `YOUR_BASE_URL` with your SCM and its base URL, for GitHub, GitLab, or Bitbucket Data Center.
+Update the `config.yaml` by replacing the SCM information containing `YOUR_BASE_URL` with your SCM and its base URL for Azure DevOps, GitHub, GitLab, or Bitbucket Data Center.
 
 <Tabs
     defaultValue="gh"