[DNS] Use APIRequest component #22328
Conversation
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryUpdated documentation to utilize the APIRequest component for API calls related to DNSSEC and zone settings.
Modified Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add |
* Replace example in /cloudflare-as-secondary/proxy-traffic.mdx * More consistent with formatting and finish cf-as-secondary * Replace DNSSEC status and multi-provider setting * dnsesec-for-primary: replace create DNSKEY example * Revert "dnsesec-for-primary: replace create DNSKEY example" This reverts commit 9d2a601. * dnsesec-for-primary: replace get ZSK example * Revert "dnsesec-for-primary: replace get ZSK example" This reverts commit 4e71662. * Replace remaining /zones/{zone_id}/dnssec PATCH examples * Replace remaining /zones/{zone_id}/dns_settings examples * Apply in dns-firewall and fix {cluster_tag} with {dns_firewall_id} * Replace /zones/{zone_id}/custom_ns examples * Replace example in partial internal-reference-zone-api.mdx
2 participants
Summary
PCX-16349