run pattern over more file extensions

Author: jacobbednarz

src/content/changelogs/ai-gateway.yaml

@@ -92,7 +92,7 @@ entries:
   - publish_date: "2024-05-09"
 
     description: |-
-      * Added new endpoints to the [REST API](/api/operations/aig-config-create-gateway).
+      * Added new endpoints to the [REST API](/api/resources/ai_gateway/methods/create/).
 
   - publish_date: "2024-03-26"
 

src/content/changelogs/api-deprecations.yaml

@@ -10,7 +10,7 @@ entries:
     description: |-
       Deprecation date: November 21, 2025
 
-      The `self_hosted_domains` field for [Access applications](https://developers.cloudflare.com/api/operations/access-applications-update-an-access-application) is deprecated in favor of `destinations` to allow for more flexibility in defining different types of domains.
+      The `self_hosted_domains` field for [Access applications](https://developers.cloudflare.com/api/resources/zero_trust/subresources/access/subresources/applications/methods/update/) is deprecated in favor of `destinations` to allow for more flexibility in defining different types of domains.
 
       Before:
       ```json
@@ -57,7 +57,7 @@ entries:
       Deprecation date: March 21, 2025
 
       The Zone Settings API endpoints for managing zone-level CNAME flattening are deprecated.
-      Instead, use the [Show DNS Settings](/api/operations/dns-settings-for-a-zone-list-dns-settings) and [Update DNS Settings](/api/operations/dns-settings-for-a-zone-update-dns-settings) endpoints to manage this setting.
+      Instead, use the [Show DNS Settings](/api/resources/dns/subresources/settings/methods/get/) and [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoints to manage this setting.
 
       Changes via the old endpoints will be reflected in the new ones, and vice versa, so there is no need to migrate existing zones. However, future API calls must use DNS Settings instead of the Zone Settings endpoints.
 
@@ -80,7 +80,7 @@ entries:
       Deprecation date: March 14, 2025
 
       The fields `"default_nameservers"` and `"use_account_custom_ns_by_default"` within the `"settings"` object of accounts are deprecated.
-      Instead, use the [Show DNS Settings](/api/operations/dns-settings-for-an-account-list-dns-settings) and [Update DNS Settings](/api/operations/dns-settings-for-an-account-update-dns-settings) endpoints to manage this setting.
+      Instead, use the [Show DNS Settings](/api/operations/dns-settings-for-an-account-list-dns-settings) and [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoints to manage this setting.
       This setting is available in the new API as `.zone_defaults.nameservers.type`, with allowed values `"cloudflare.standard"`, `"cloudflare.standard.random"`, `"custom.account"` and `"custom.tenant"`.
 
       Changes via the old endpoints will be reflected in the new ones, and vice versa, so there is no need to migrate existing zones. However, future API calls must use DNS Settings instead of the Accounts endpoints.
@@ -283,7 +283,7 @@ entries:
 
       The dedicated endpoints for DNS settings `use_apex_ns` and `secondary_overrides` are being deprecated.
 
-      Instead, use the [Show DNS Settings](/api/operations/dns-settings-for-a-zone-list-dns-settings) and [Update DNS Settings](/api/operations/dns-settings-for-a-zone-update-dns-settings) endpoints to manage these settings.
+      Instead, use the [Show DNS Settings](/api/resources/dns/subresources/settings/methods/get/) and [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoints to manage these settings.
 
       - Instead of the `.../use_apex_ns` endpoint, use the `multi_provider` field.
       - Instead of the `.../secondary_overrides` endpoint, use the `secondary_overrides` field.
@@ -371,7 +371,7 @@ entries:
 
       The complete name would then be, e.g., `_xmpp._tcp.example.com`.
 
-      When interacting with DNS records through the [API](/api/operations/dns-records-for-a-zone-create-dns-record), SRV records contain both a full `name` as well as a `data` map containing the individual components of the name:
+      When interacting with DNS records through the [API](/api/resources/dns/subresources/records/methods/create/), SRV records contain both a full `name` as well as a `data` map containing the individual components of the name:
 
       ```txt
       {

src/content/changelogs/byoip.yaml

@@ -7,4 +7,4 @@ productAreaLink: /fundamentals/reference/changelog/performance/
 entries:
   - publish_date: "2024-07-02"
     title: Address Maps for BYOIP and Static IPs
-    description: Address Maps is available via [API](/api/operations/ip-address-management-address-maps-list-address-maps) and via [dashboard](https://dash.cloudflare.com/?to=/:account/ip-addresses/proxy-ips). Address Maps allows customers with BYOIP prefixes or account-level Static IPs to specify which IP addresses should be mapped to DNS records when they are proxied through Cloudflare. Refer to the [documentation](/byoip/address-maps/) for details.
+    description: Address Maps is available via [API](/api/resources/addressing/subresources/address_maps/methods/list/) and via [dashboard](https://dash.cloudflare.com/?to=/:account/ip-addresses/proxy-ips). Address Maps allows customers with BYOIP prefixes or account-level Static IPs to specify which IP addresses should be mapped to DNS records when they are proxied through Cloudflare. Refer to the [documentation](/byoip/address-maps/) for details.

src/content/changelogs/d1.yaml

@@ -26,7 +26,7 @@ entries:
   - publish_date: "2024-06-17"
     title: HTTP API now returns a HTTP 429 error for overloaded D1 databases
     description: |-
-      Previously, D1's [HTTP API](/api/operations/cloudflare-d1-query-database) returned a HTTP `500 Internal Server` error for queries that came in while a D1 database was overloaded. These requests now correctly return a `HTTP 429 Too Many Requests` error.
+      Previously, D1's [HTTP API](/api/resources/d1/subresources/database/methods/query/) returned a HTTP `500 Internal Server` error for queries that came in while a D1 database was overloaded. These requests now correctly return a `HTTP 429 Too Many Requests` error.
 
       D1's [Workers API](/d1/worker-api/) is unaffected by this change.
 
@@ -40,7 +40,7 @@ entries:
   - publish_date: "2024-04-12"
     title: HTTP API now returns a HTTP 400 error for invalid queries
     description: |-
-      Previously, D1's [HTTP API](/api/operations/cloudflare-d1-query-database) returned a HTTP `500 Internal Server` error for an invalid query. An invalid SQL query now correctly returns a `HTTP 400 Bad Request` error.
+      Previously, D1's [HTTP API](/api/resources/d1/subresources/database/methods/query/) returned a HTTP `500 Internal Server` error for an invalid query. An invalid SQL query now correctly returns a `HTTP 400 Bad Request` error.
 
       D1's [Workers API](/d1/worker-api/) is unaffected by this change.
 

src/content/changelogs/gateway.yaml

@@ -36,7 +36,7 @@ entries:
   - publish_date: "2024-06-25"
     title: Gateway DNS policy setting to ignore CNAME category matches
     description: |-
-      Gateway now offers the ability to selectively ignore CNAME domain categories in DNS policies via the [**Ignore CNAME domain categories** setting](/cloudflare-one/policies/gateway/domain-categories/#ignore-cname-domain-categories) in the policy builder and the [`ignore_cname_category_matches` setting](/api/operations/zero-trust-gateway-rules-create-zero-trust-gateway-rule) in the API.
+      Gateway now offers the ability to selectively ignore CNAME domain categories in DNS policies via the [**Ignore CNAME domain categories** setting](/cloudflare-one/policies/gateway/domain-categories/#ignore-cname-domain-categories) in the policy builder and the [`ignore_cname_category_matches` setting](/api/resources/zero_trust/subresources/gateway/subresources/rules/methods/create/) in the API.
   - publish_date: "2024-04-05"
     title: Gateway file type control improvements
     description: |-

src/content/changelogs/kv.yaml

@@ -9,7 +9,7 @@ entries:
     title: Workers KV REST API bulk operations provide granular errors
     description: |-
 
-      The REST API endpoints for bulk operations ([write](/api/operations/workers-kv-namespace-write-multiple-key-value-pairs), [delete](/api/operations/workers-kv-namespace-delete-multiple-key-value-pairs)) now return the keys of operations that failed during the bulk operation. The updated response bodies are documented in the [REST API documentation](/api/operations/workers-kv-namespace-list-namespaces) and contain the following information in the `result` field:
+      The REST API endpoints for bulk operations ([write](/api/resources/kv/subresources/namespaces/methods/bulk_update/), [delete](/api/resources/kv/subresources/namespaces/methods/bulk_delete/)) now return the keys of operations that failed during the bulk operation. The updated response bodies are documented in the [REST API documentation](/api/resources/kv/subresources/namespaces/methods/list/) and contain the following information in the `result` field:
 
       ```
       {
@@ -26,5 +26,5 @@ entries:
 
       Workers KV now has a new [metrics dashboard](/kv/observability/metrics-analytics/#view-metrics-in-the-dashboard) and [analytics API](/kv/observability/metrics-analytics/#query-via-the-graphql-api) that leverages the [GraphQL Analytics API](/analytics/graphql-api/) used by many other Cloudflare products. The new analytics API provides per-account and per-namespace metrics for both operations and storage, including latency metrics for read and write operations to Workers KV.
 
-      The legacy Workers KV [analytics REST API](/api/operations/workers-kv-request-analytics-query-request-analytics) will be turned off as of January 31st, 2025.
+      The legacy Workers KV [analytics REST API](/api/resources/kv/subresources/namespaces/subresources/analytics/methods/list/) will be turned off as of January 31st, 2025.
       Developers using this API will receive a series of email notifications prior to the shutdown of the legacy API.

src/content/changelogs/r2.yaml

@@ -28,10 +28,10 @@ entries:
       - R2 [`bucket domain` command](/workers/wrangler/commands/#domain-add) added to Wrangler. Supports listing, adding, removing, and updating [R2 bucket custom domains](/r2/buckets/public-buckets/#custom-domains).
   - publish_date: "2024-11-01"
     description: |-
-      - Add `minTLS` to response of [list custom domains](/api/operations/r2-list-custom-domains) endpoint.
+      - Add `minTLS` to response of [list custom domains](/api/resources/r2/subresources/buckets/subresources/domains/subresources/custom/methods/list/) endpoint.
   - publish_date: "2024-10-28"
     description: |-
-      - Add [get custom domain](/api/operations/r2-get-custom-domain-settings) endpoint.
+      - Add [get custom domain](/api/resources/r2/subresources/buckets/subresources/domains/subresources/custom/methods/get/) endpoint.
   - publish_date: "2024-10-21"
     description: |-
       - Event notifications can now be configured for R2 buckets in [jurisdictions](/r2/reference/data-location/#jurisdictional-restrictions) (e.g., EU, FedRAMP).
@@ -43,7 +43,7 @@ entries:
       - Add the ability to set and [update minimum TLS version](/r2/buckets/public-buckets/#minimum-tls-version) for R2 bucket custom domains.
   - publish_date: "2024-08-26"
     description: |-
-      - Added support for configuring R2 bucket custom domains via [API](/api/operations/r2-add-custom-domain).
+      - Added support for configuring R2 bucket custom domains via [API](/api/resources/r2/subresources/buckets/subresources/domains/subresources/custom/methods/create/).
   - publish_date: "2024-08-21"
     description: |-
       - [Sippy](/r2/data-migration/sippy/) is now generally available. Metrics for ongoing migrations can now be found in the dashboard or via the GraphQL analytics API.
@@ -64,7 +64,7 @@ entries:
       - Added support for [Infrequent Access](/r2/buckets/storage-classes/) storage class (beta).
   - publish_date: "2024-05-24"
     description: |-
-      - Added [create temporary access tokens](/api/operations/r2-create-temp-access-credentials) endpoint.
+      - Added [create temporary access tokens](/api/resources/r2/subresources/temporary_credentials/methods/create/) endpoint.
   - publish_date: "2024-04-03"
     description: |-
       - [Event notifications](/r2/buckets/event-notifications/) for R2 is now available as an open beta.
@@ -79,7 +79,7 @@ entries:
       - The shape of the configuration object when modifying Sippy's configuration has changed.
   - publish_date: "2024-02-02"
     description: |-
-      - Updated [GetBucket](/api/operations/r2-get-bucket) endpoint: Now fetches by `bucket_name` instead of `bucket_id`.
+      - Updated [GetBucket](/api/resources/r2/subresources/buckets/methods/get/) endpoint: Now fetches by `bucket_name` instead of `bucket_id`.
   - publish_date: "2024-01-30"
     description: |-
       - Fixed a bug where the API would accept empty strings in the `AllowedHeaders` property of `PutBucketCors` actions.
@@ -115,14 +115,14 @@ entries:
       hashes.
   - publish_date: "2023-06-16"
     description: |-
-      - Fixed a bug where calling [GetBucket](/api/operations/r2-get-bucket) on a non-existent bucket would return a 500 instead of a 404.
+      - Fixed a bug where calling [GetBucket](/api/resources/r2/subresources/buckets/methods/get/) on a non-existent bucket would return a 500 instead of a 404.
       - Improved S3 compatibility for ListObjectsV1, now nextmarker is only set when truncated is true.
       - The R2 worker bindings now support parsing conditional headers with multiple etags. These etags can now be strong, weak or a wildcard. Previously the bindings only accepted headers containing a single strong etag.
       - S3 putObject now supports sha256 and sha1 checksums. These were already supported by the R2 worker bindings.
       - CopyObject in the S3 compatible api now supports Cloudflare specific headers which allow the copy operation to be conditional on the state of the destination object.
   - publish_date: "2023-04-01"
     description: |-
-      - [GetBucket](/api/operations/r2-get-bucket) is now available for use through the Cloudflare API.
+      - [GetBucket](/api/resources/r2/subresources/buckets/methods/get/) is now available for use through the Cloudflare API.
       - [Location hints](https://developers.cloudflare.com/r2/reference/data-location/) can now be set when creating a bucket, both through the S3 API, and the dashboard.
   - publish_date: "2023-03-16"
     description: |-