Use partials for repeated API steps (part 2)

Author: pedrosousa

src/content/docs/waf/managed-rules/reference/exposed-credentials-check.mdx

@@ -52,7 +52,10 @@ To enable the Cloudflare Exposed Credentials Check Managed Ruleset for a given z
 
 This example deploys the Cloudflare Exposed Credentials Check Managed Ruleset to the `http_request_firewall_managed` phase of a given zone (`{zone_id}`) by creating a rule that executes the managed ruleset. The rules in the managed ruleset are executed for all incoming requests.
 
-1.  Invoke the [Get a zone entry point ruleset](/api/operations/getZoneEntrypointRuleset) operation to obtain the definition of the entry point ruleset for the `http_request_firewall_managed` phase. You will need the [zone ID](/fundamentals/setup/find-account-and-zone-ids/) for this task.
+1.  <Render
+    	file="rulesets/api-zone/step1-get-entrypoint"
+    	params={{ phaseName: "http_request_firewall_managed" }}
+    />
 
     ```bash
     curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/rulesets/phases/http_request_firewall_managed/entrypoint" \
@@ -80,7 +83,13 @@ This example deploys the Cloudflare Exposed Credentials Check Managed Ruleset to
     }
     ```
 
-2.  If the entry point ruleset already exists (that is, if you received a `200 OK` status code and the ruleset definition), take note of the ruleset ID in the response. Then, invoke the [Create a zone ruleset rule](/api/operations/createZoneRulesetRule) operation to add an `execute` rule to the existing ruleset deploying the Cloudflare Exposed Credentials Check Managed Ruleset (with ID <RuleID id="c2e184081120413c86c3ab7e14069605" />). By default, the rule will be added at the end of the list of rules already in the ruleset.
+2.  <Render
+    	file="rulesets/api-zone/step2-create-rule"
+    	params={{
+    		deploymentItem:
+    			"Cloudflare Exposed Credentials Check Managed Ruleset (with ID `c2e184081120413c86c3ab7e14069605`)",
+    	}}
+    />
 
     ```bash
     curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/rulesets/{ruleset_id}/rules" \
@@ -130,7 +139,14 @@ This example deploys the Cloudflare Exposed Credentials Check Managed Ruleset to
     }
     ```
 
-3.  If the entry point ruleset does not exist (that is, if you received a `404 Not Found` status code in step 1), create it using the [Create a zone ruleset](/api/operations/createZoneRuleset) operation. Include a single rule in the `rules` array that executes the Cloudflare Exposed Credentials Check Managed Ruleset (with ID <RuleID id="c2e184081120413c86c3ab7e14069605" />) for all incoming requests in the zone.
+3.  <Render
+    	file="rulesets/api-zone/step3-create-ruleset"
+    	params={{
+    		deploymentItem:
+    			"Cloudflare Exposed Credentials Check Managed Ruleset (with ID `c2e184081120413c86c3ab7e14069605`)",
+    		scope: "all incoming requests in the zone",
+    	}}
+    />
 
     ```bash
     curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/rulesets" \

src/content/docs/waf/managed-rules/reference/sensitive-data-detection.mdx

@@ -48,7 +48,10 @@ To enable Cloudflare Sensitive Data Detection for a given zone using the API, cr
 
 This example deploys the Cloudflare Sensitive Data Detection managed ruleset to the `http_response_firewall_managed` phase of a given zone (`{zone_id}`) by creating a rule that executes the managed ruleset. The rules in the managed ruleset are executed for all incoming requests.
 
-1.  Invoke the [Get a zone entry point ruleset](/api/operations/getZoneEntrypointRuleset) operation to obtain the definition of the entry point ruleset for the `http_response_firewall_managed` phase. You will need the [zone ID](/fundamentals/setup/find-account-and-zone-ids/) for this task.
+1.  <Render
+    	file="rulesets/api-zone/step1-get-entrypoint"
+    	params={{ phaseName: "http_response_firewall_managed" }}
+    />
 
     ```bash
     curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/rulesets/phases/http_response_firewall_managed/entrypoint" \
@@ -76,7 +79,13 @@ This example deploys the Cloudflare Sensitive Data Detection managed ruleset to
     }
     ```
 
-2.  If the entry point ruleset already exists (that is, if you received a `200 OK` status code and the ruleset definition), take note of the ruleset ID in the response. Then, invoke the [Create a zone ruleset rule](/api/operations/createZoneRulesetRule) operation to add an `execute` rule to the existing ruleset deploying the Cloudflare Sensitive Data Detection managed ruleset (with ID <RuleID id="e22d83c647c64a3eae91b71b499d988e" />). By default, the rule will be added at the end of the list of rules already in the ruleset.
+2.  <Render
+    	file="rulesets/api-zone/step2-create-rule"
+    	params={{
+    		deploymentItem:
+    			"Cloudflare Sensitive Data Detection managed ruleset (with ID `e22d83c647c64a3eae91b71b499d988e`)",
+    	}}
+    />
 
     ```bash
     curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/rulesets/{ruleset_id}/rules" \
@@ -126,7 +135,14 @@ This example deploys the Cloudflare Sensitive Data Detection managed ruleset to
     }
     ```
 
-3.  If the entry point ruleset does not exist (that is, if you received a `404 Not Found` status code in step 1), create it using the [Create a zone ruleset](/api/operations/createZoneRuleset) operation. Include a single rule in the `rules` array that executes the Cloudflare Sensitive Data Detection managed ruleset (with ID <RuleID id="e22d83c647c64a3eae91b71b499d988e" />) for all incoming requests in the zone.
+3.  <Render
+    	file="rulesets/api-zone/step3-create-ruleset"
+    	params={{
+    		deploymentItem:
+    			"Cloudflare Sensitive Data Detection managed ruleset (with ID `e22d83c647c64a3eae91b71b499d988e`)",
+    		scope: "all incoming requests in the zone",
+    	}}
+    />
 
     ```bash
     curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/rulesets" \