Documents connect being shut off when outbound worker is used

[mikenomitch]

Summary

When an outbound workers is on, the connect() API no longer works. This adds a note to the documentation explaining this.

In the long-run, we may add an outboundConnect-like API to allow the platform user to handle outbound TCP or allow them to turn it on/off with a toggle. If we do that, then this should be reverted or changed.

Screenshot

Documentation checklist

• The documentation style guide has been adhered to.

[hyperlint-ai]

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

Updated documentation to clarify the impact of enabling outbound workers on the connect() API functionality.

• Added a note explaining that the connect() API is disabled when outbound workers are enabled.
• Mentioned potential future enhancements regarding outbound TCP handling.
• Ensured adherence to the documentation style guide.

Modified Files

• src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers.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.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
/src/content/docs/cloudflare-for-platforms/workers-for-platforms/	@irvinebroque, @angelampcosta, @GregBrimble, @cloudflare/deploy-config, @cloudflare/pcx-technical-writing

[github-actions]

Preview URL: https://98f3038f.preview.developers.cloudflare.com
Preview Branch URL: https://mikenomitch-connect-wfp.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers/	https://mikenomitch-connect-wfp.preview.developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers/

[angelampcosta]

@mikenomitch can I merge the PR?

[irvinebroque]

does this mean you can't use hyperdrive when outbound workers are enabled?

glad we are documenting but this feels like just a bug, since afaik outbound workers were only ever intended to intercept fetch() in the first place.

maybe another example of where pipelines and complexity that falls out from that hurts us

@dinasaur404 fyi for context re: bringing outbound workers to workers