Skip to content

[ZT] Clarify device profiles in egress policy config #22072

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 29, 2025
Merged

Conversation

ranbel
Copy link
Contributor

@ranbel ranbel commented Apr 29, 2025

No description provided.

@ranbel ranbel requested review from maxvp and a team as code owners April 29, 2025 20:13
Copy link
Contributor

hyperlint-ai bot commented Apr 29, 2025

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 Summary

Clarified the reference to device profiles in the egress policy configuration for WARP.

  • Updated the reference to 'WARP Connector device profile' to 'WARP device profile' for clarity.
  • Maintained instructions for configuring Split Tunnel settings in the egress policy.

Modified Files

  • src/content/docs/cloudflare-one/policies/gateway/egress-policies/index.mdx

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 hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

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 hyperlint-ignore to the PR to ignore the link check for this PR.

@ranbel ranbel merged commit 3e2ecac into production Apr 29, 2025
14 checks passed
@ranbel ranbel deleted the ranbel-patch-2 branch April 29, 2025 20:26
GregBrimble pushed a commit that referenced this pull request May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants