Replace account ID variable

Author: maxvp

src/content/docs/cloudflare-one/applications/configure-apps/dash-sso-apps.mdx

@@ -73,7 +73,7 @@ If there is an issue with your SSO IdP provider, you can add an alternate IdP us
 1. [Add](/api/resources/zero_trust/subresources/identity_providers/methods/create/) one-time PIN login:
 
 ```bash title="cURL command"
-curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/access/identity_providers' \
+curl 'https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/identity_providers' \
 --header "X-Auth-Email: <EMAIL>" \
 --header "X-Auth-Key: <API_KEY>" \
 --header "Content-Type: application/json" \
@@ -86,7 +86,7 @@ curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/access/identity
 2. [Get](/api/resources/zero_trust/subresources/access/subresources/applications/methods/list/) the `id` of the `dash_sso` Access application. You can use [`jq`](https://jqlang.github.io/jq/download/) to quickly find the correct application:
 
 ```bash title="cURL command"
-curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/access/apps' \
+curl 'https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/apps' \
 --header "X-Auth-Email: <EMAIL>" \
 --header "X-Auth-Key: <API_KEY>" \
 | jq '.result[] | select(.type == "dash_sso")'
@@ -106,7 +106,7 @@ curl 'https://api.cloudflare.com/client/v4/accounts/{account_id}/access/apps' \
 
 ```bash title="cURL command"
 curl --request PUT \
-'https://api.cloudflare.com/client/v4/accounts/{account_id}/access/apps/3537a672-e4d8-4d89-aab9-26cb622918a1' \
+'https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/apps/3537a672-e4d8-4d89-aab9-26cb622918a1' \
 --header "X-Auth-Email: <EMAIL>" \
 --header "X-Auth-Key: <API_KEY>" \
 --header "Content-Type: application/json" \
@@ -127,7 +127,7 @@ The following API calls will disable SSO enforcement for an account. This action
 1. Get your SSO `connector_id`:
 
 ```bash title="cURL command"
-curl https://api.cloudflare.com/client/v4/accounts/{account_id}/sso/v2/connectors \
+curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/sso/v2/connectors \
 --header "X-Auth-Email: <EMAIL>" \
 --header "X-Auth-Key: <API_KEY>"
 ```
@@ -153,7 +153,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/sso/v2/connector
 
 ```bash title="cURL command"
 curl --request PATCH \
-'https://api.cloudflare.com/client/v4/accounts/{account_id}/sso/v2/connectors/2828' \
+'https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/sso/v2/connectors/2828' \
 --header "X-Auth-Email: <EMAIL>" \
 --header "X-Auth-Key: <API_KEY>" \
 --header "Content-Type: application/json" \

src/content/docs/cloudflare-one/connections/connect-devices/agentless/dns/dns-over-https.mdx

@@ -114,7 +114,7 @@ Currently, authentication tokens can only be generated through the API. You can
 ### 1. Create a service token for the account
 
 ```bash
-curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/access/service_tokens" \
+curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/service_tokens" \
 --header "X-Auth-Email: <EMAIL>" \
 --header "X-Auth-Key: <API_KEY>" \
 --header "Content-Type: application/json" \
@@ -148,12 +148,12 @@ Save the service token's `client_id`, `client_secret`, and `id`.
 
 ```bash
 curl --request PUT \
-"https://api.cloudflare.com/client/v4/accounts/{account_id}/access/organizations/doh/{service_token_id}" \
+"https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/organizations/doh/$SERVICE_TOKEN_ID" \
 --header "X-Auth-Email: <EMAIL>" \
 --header "X-Auth-Key: <API_KEY>"
 ```
 
-If you get an `access.api.error.service_token_not_found` error, check that `{service_token_id}` is the value of `id` and not `client_id`.
+If you get an `access.api.error.service_token_not_found` error, check that `$SERVICE_TOKEN_ID` is the value of `id` and not `client_id`.
 
 <Details header="Example response">
 
@@ -181,7 +181,7 @@ If you get an `access.api.error.service_token_not_found` error, check that `{ser
 Create a new user and optionally add them to a group.
 
 ```bash
-curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/access/users" \
+curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/access/users" \
 --header "X-Auth-Email: <EMAIL>" \
 --header "X-Auth-Key: <API_KEY>" \
 --header "Content-Type: application/json" \

src/content/docs/cloudflare-one/connections/connect-devices/agentless/pac-files.mdx

@@ -211,7 +211,7 @@ To get the domain of a proxy endpoint:
 1. Use the [List proxy endpoints](/api/resources/zero_trust/subresources/gateway/subresources/proxy_endpoints/methods/list/) operation to get a list of your proxy endpoints and their details. For example:
 
    ```bash
-   curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/proxy_endpoints \
+   curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/gateway/proxy_endpoints \
    --header "Authorization: Bearer <API_TOKEN>"
    ```
 

src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles.mdx

@@ -35,7 +35,7 @@ Your profile will appear in the **Profile settings** list. You can rearrange the
 Send a `POST` request to the [Devices endpoint](/api/resources/zero_trust/subresources/devices/subresources/policies/subresources/custom/methods/create/):
 
 ```bash
-curl https://api.cloudflare.com/client/v4/accounts/{account_id}/devices/policy \
+curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/devices/policy \
 --header "X-Auth-Email: <EMAIL>" \
 --header "X-Auth-Key: <API_KEY>" \
 --header "Content-Type: application/json" \

src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/remote-management.mdx

@@ -49,11 +49,12 @@ On Linux, Cloudflare Tunnel installs itself as a system service using `systemctl
 
 4. To verify the new configuration, check the service status:
 
-	```sh
-	sudo systemctl status cloudflared
-	```
-	```sh output
-	● cloudflared.service - cloudflared
+   ```sh
+   sudo systemctl status cloudflared
+   ```
+
+   ```sh output
+   ● cloudflared.service - cloudflared
      Loaded: loaded (/etc/systemd/system/cloudflared.service; enabled; preset: enabled)
      Active: active (running) since Wed 2024-10-09 20:02:59 UTC; 2s ago
    Main PID: 2157 (cloudflared)
@@ -62,7 +63,7 @@ On Linux, Cloudflare Tunnel installs itself as a system service using `systemctl
         CPU: 136ms
      CGroup: /system.slice/cloudflared.service
              └─2157 /usr/bin/cloudflared tunnel --loglevel debug --logfile /var/log/cloudflared/cloudflared.log run --token eyJhIjoi...
-	```
+   ```
 
 </TabItem> <TabItem label="macOS">
 
@@ -186,85 +187,88 @@ To rotate a tunnel token:
 
 1. Refresh the token on Cloudflare:
 
-	<Tabs syncKey="dashPlusAPI">
-	<TabItem label="Dashboard">
-	1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels**.
-	2. Select a `cloudflared` tunnel and select **Edit**.
-	3. Select **Refresh token**.
-	4. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
-
-	</TabItem>
-	<TabItem label="API">
-
-	1. Generate a random base64 string (minimum size 32 bytes) to use as a tunnel secret:
-
-		```sh
-		openssl rand -base64 32
-		```
-
-		```sh output
-		AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=
-		```
-
-	2. Make a `PATCH` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/methods/edit/) endpoint:
-		```sh
-		curl --request PATCH \
-		https://api.cloudflare.com/client/v4/accounts/{account_id}/cfd_tunnel/{tunnel_id} \
-		--header 'Content-Type: application/json' \
-		--header "Authorization: Bearer <API_TOKEN>" \
-		--data '{
-			"name": "Example tunnel",
-			"tunnel_secret": "AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg="
-		}'
-		```
-
-		```sh output {18}
-		{
-			"success": true,
-			"errors": [],
-			"messages": [],
-			"result": {
-				"id": "f70ff985-a4ef-4643-bbbc-4a0ed4fc8415",
-				"account_tag": "699d98642c564d2e855e9661899b7252",
-				"created_at": "2024-12-04T22:03:26.291225Z",
-				"deleted_at": null,
-				"name": "Example tunnel",
-				"connections": [],
-				"conns_active_at": null,
-				"conns_inactive_at": "2024-12-04T22:03:26.291225Z",
-				"tun_type": "cfd_tunnel",
-				"metadata": {},
-				"status": "inactive",
-				"remote_config": true,
-				"token": "eyJhIjoiNWFiNGU5Z..."
-			}
-		}
-		```
-	3. Copy the `token` value shown in the output.
-
-	</TabItem>
-	</Tabs>
-
-	After refreshing the token, `cloudflared` can no longer establish new connections to Cloudflare using the old token. However, existing connectors will remain active and the tunnel will continue serving traffic.
+   <Tabs syncKey="dashPlusAPI">
+<TabItem label="Dashboard">
+1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels**.
+2. Select a `cloudflared` tunnel and select **Edit**.
+3. Select **Refresh token**.
+4. Copy the `cloudflared` installation command for your operating system. This command contains the new token.
+
+   </TabItem>
+<TabItem label="API">
+
+   1. Generate a random base64 string (minimum size 32 bytes) to use as a tunnel secret:
+
+      ```sh
+      openssl rand -base64 32
+      ```
+
+      ```sh output
+      AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg=
+      ```
+
+   2. Make a `PATCH` request to the [Cloudflare Tunnel](/api/resources/zero_trust/subresources/tunnels/methods/edit/) endpoint:
+
+      ```sh
+      curl --request PATCH \
+      https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/cfd_tunnel/{tunnel_id} \
+      --header 'Content-Type: application/json' \
+      --header "Authorization: Bearer <API_TOKEN>" \
+      --data '{
+      	"name": "Example tunnel",
+      	"tunnel_secret": "AQIDBAUGBwgBAgMEBQYHCAECAwQFBgcIAQIDBAUGBwg="
+      }'
+      ```
+
+      ```sh output {18}
+      {
+      	"success": true,
+      	"errors": [],
+      	"messages": [],
+      	"result": {
+      		"id": "f70ff985-a4ef-4643-bbbc-4a0ed4fc8415",
+      		"account_tag": "699d98642c564d2e855e9661899b7252",
+      		"created_at": "2024-12-04T22:03:26.291225Z",
+      		"deleted_at": null,
+      		"name": "Example tunnel",
+      		"connections": [],
+      		"conns_active_at": null,
+      		"conns_inactive_at": "2024-12-04T22:03:26.291225Z",
+      		"tun_type": "cfd_tunnel",
+      		"metadata": {},
+      		"status": "inactive",
+      		"remote_config": true,
+      		"token": "eyJhIjoiNWFiNGU5Z..."
+      	}
+      }
+      ```
+
+   3. Copy the `token` value shown in the output.
+
+   </TabItem>
+</Tabs>
+
+   After refreshing the token, `cloudflared` can no longer establish new connections to Cloudflare using the old token. However, existing connectors will remain active and the tunnel will continue serving traffic.
 
 2. On half of your `cloudflared` replicas, update `cloudflared` to use the new token. For example, on a Linux host:
 
-	```sh
-	sudo cloudflared service install <TOKEN>
-	```
+   ```sh
+   sudo cloudflared service install <TOKEN>
+   ```
 
 3. Restart `cloudflared`:
 
-	```sh
-	sudo systemctl restart cloudflared.service
-	```
+   ```sh
+   sudo systemctl restart cloudflared.service
+   ```
 
 4. Confirm that the service started correctly:
-	```sh
-	sudo systemctl status cloudflared
-	```
 
-	While these replicas are connecting to Cloudflare with the new token, traffic will automatically route through the other replicas.
+   ```sh
+   sudo systemctl status cloudflared
+   ```
+
+   While these replicas are connecting to Cloudflare with the new token, traffic will automatically route through the other replicas.
 
 5. Wait 10 minutes for traffic to route through the new connectors.
 
@@ -278,29 +282,31 @@ If your tunnel token is compromised, we recommend taking the following steps:
 
 1. Refresh the token using the dashboard or API. Refer to Step 1 of [Rotate a token without service disruption](#rotate-a-token-without-service-disruption).
 2. [Delete all connections](/api/resources/zero_trust/subresources/tunnels/subresources/connections/methods/delete/) between `cloudflared` and Cloudflare:
-	```sh
-	curl --request DELETE \
-	https://api.cloudflare.com/client/v4/accounts/{account_id}/cfd_tunnel/{tunnel_id}/connections \
-	--header "Authorization: Bearer <API_TOKEN>"
-	```
 
-	This will clean up any unauthorized connections and prevent users from connecting to your network.
+   ```sh
+   curl --request DELETE \
+   https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/cfd_tunnel/{tunnel_id}/connections \
+   --header "Authorization: Bearer <API_TOKEN>"
+   ```
+
+   This will clean up any unauthorized connections and prevent users from connecting to your network.
 
 3. On each `cloudflared` replica, update `cloudflared` to use the new token. For example, on a Linux host:
 
-	```sh
-	sudo cloudflared service install <TOKEN>
-	```
+   ```sh
+   sudo cloudflared service install <TOKEN>
+   ```
+
 4. Restart `cloudflared`:
 
-	```sh
-	sudo systemctl restart cloudflared.service
-	```
+   ```sh
+   sudo systemctl restart cloudflared.service
+   ```
 
 5. Confirm that the service started correctly:
-	```sh
-	sudo systemctl status cloudflared
-	```
+   ```sh
+   sudo systemctl status cloudflared
+   ```
 
 The tunnel token is now fully rotated. The old token is no longer in use.
 

src/content/docs/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx

@@ -13,7 +13,10 @@ import { Tabs, TabItem, Badge, Render } from "~/components";
 
 [Access for Infrastructure](/cloudflare-one/applications/non-http/infrastructure-apps/) provides granular control over how users can connect to your SSH servers. This feature uses the same deployment model as [WARP-to-Tunnel](/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-warp-to-tunnel/) but unlocks more policy options and command logging functionality.
 
-<Render file="access/short-lived-certs-intro" params={{ intro: "Furthermore, Access for Infrastructure replaces" }} />
+<Render
+	file="access/short-lived-certs-intro"
+	params={{ intro: "Furthermore, Access for Infrastructure replaces" }}
+/>
 
 ## 1. Connect the server to Cloudflare
 
@@ -31,8 +34,7 @@ To connect your devices to Cloudflare:
 
 ## 3. Route server IPs through WARP
 
-<Render file="tunnel/warp-to-tunnel-route-ips" params={{ one: "SSH server"}} />
-
+<Render file="tunnel/warp-to-tunnel-route-ips" params={{ one: "SSH server" }} />
 
 ## 4. Add a target
 
@@ -55,9 +57,11 @@ To generate a Cloudflare SSH CA and get its public key:
 <Render file="ssh/ssh-proxy-ca" />
 
 ### Save the public key
+
 <Render file="ssh/public-key" />
 
 ### Modify your SSHD config
+
 <Render file="ssh/modify-sshd" />
 
 :::note
@@ -66,9 +70,11 @@ For certain distributions, such as Amazon Linux 1 (based on RHEL), the certifica
 ```sh
 chmod 600 /etc/ssh/ca.pub
 ```
+
 :::
 
 ### Restart your SSH server
+
 <Render file="ssh/restart-server" />
 
 ## 7. Connect as a user
@@ -112,13 +118,14 @@ Cloudflare will stop logging SSH commands to your targets, as well as any comman
 To delete the SSH encryption public key using the [API](/api/resources/zero_trust/subresources/gateway/subresources/audit_ssh_settings/methods/update/):
 
 ```sh
-curl --request PUT https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/audit_ssh_settings \
+curl --request PUT https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/gateway/audit_ssh_settings \
 --header "X-Auth-Email: <EMAIL>" \
 --header "X-Auth-Key: <API_KEY>" \
 --data '{
   "public_key": ""
 }'
 ```
+
 </TabItem>
 </Tabs>