Skip to content

DOCS-818: Expand Target DNS guidance#267

Open
harrison-akeyless wants to merge 5 commits into
v1.0from
v1.0_docs-818-lets-encrypt-azure-example
Open

DOCS-818: Expand Target DNS guidance#267
harrison-akeyless wants to merge 5 commits into
v1.0from
v1.0_docs-818-lets-encrypt-azure-example

Conversation

@harrison-akeyless
Copy link
Copy Markdown
Collaborator

Summary

  • add an Azure DNS managed identity example for Let's Encrypt DNS-01 flows
  • document how to create an Azure target with Gateway cloud identity
  • add an Azure DNS challenge troubleshooting checklist

Validation

  • npx markdownlint-cli2 --fix --config .github/markdownlint/.markdownlint-cli2.yaml --no-globs "docs/Secrets Management/targets/lets-encrypt.md"
  • npx markdownlint-cli2 --config .github/markdownlint/.markdownlint-cli2.yaml --no-globs "docs/Secrets Management/targets/lets-encrypt.md"
  • npx cspell --config cspell.config.yaml --no-progress "docs/Secrets Management/targets/lets-encrypt.md"
  • lychee --verbose --no-progress --exclude-file ".github/lychee/.lycheeignore" --exclude-path ".github" --exclude-link-local --exclude-loopback --include-mail "docs/Secrets Management/targets/lets-encrypt.md"

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 22, 2026

Warning

Rate limit exceeded

@harrison-akeyless has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 40 minutes and 8 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3c403b40-8815-4cc6-a1f9-1f49d3ee0fbf

📥 Commits

Reviewing files that changed from the base of the PR and between acfc19e and bcaa0b9.

📒 Files selected for processing (3)
  • docs/Secrets Management/targets/digicert-target.md
  • docs/Secrets Management/targets/google-ca-target.md
  • docs/Secrets Management/targets/lets-encrypt.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch v1.0_docs-818-lets-encrypt-azure-example

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@harrison-akeyless harrison-akeyless changed the title DOCS-818: Expand Let's Encrypt Azure DNS guidance DOCS-818: Expand Target DNS guidance May 22, 2026
@harrison-akeyless harrison-akeyless marked this pull request as ready for review May 22, 2026 16:52
Copy link
Copy Markdown
Contributor

@Avi-Akeyless Avi-Akeyless left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@harrison-akeyless Looks good, just few notes:

  1. We don't have the timeout option in the console so we can take it off (if it will be added to the target we'll add it to the doc).
  2. Cloudflare is also supported from the consle, not only from the CLI, so the note about it can be removed and it can be added to the DNS provider list.
  3. The "Click Finish" step marked as 1, and it's the last step for creating the target from the console.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants