Document accept_http and update HTTP operators#212
Document accept_http and update HTTP operators#212mavam wants to merge 12 commits intotopic/new-executorfrom
Conversation
|
📦 Preview · View → · 🟢 Live Auto-updates on push |
592fd96 to
8b171ef
Compare
8c59ee1 to
3886444
Compare
588262f to
17b8b2b
Compare
8b171ef to
15faf9d
Compare
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment Tip You can disable sequence diagrams in the walkthrough.Disable the |
Add documentation for the new `accept_http` operator that starts an HTTP server and forwards incoming requests as events. Update `from_http` to reflect its new client-only design with the `$response` pipeline variable replacing `metadata_field`, and the removal of `server=true` mode. Add `accept_http` to the See Also section of the `http` operator. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Replace `metadata_field` with `$response` variable for `from_http`
- Move lambda pagination examples to `http` operator (from_http only
supports `paginate="link"` now)
- Fix TLS syntax to use `tls={...}` record format
- Fix incorrect parameter names (`max_retries` -> `max_retry_count`,
`timeout` -> `connection_timeout`)
- Update data enrichment and error handling examples
- Clarify which features are `from_http`-only vs `http`-only
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Restructure around use cases: fetching data, accepting requests, and sending data. Add accept_http coverage, TLS examples for both client and server, and webhook/enrichment/pagination examples. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Remove duplicated examples and link to the guide instead. Keep the page focused on explaining what operators exist and when to use each. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add a section explaining that from_http and http are both HTTP clients
with nearly identical options, differing only in being a source vs
transformation operator.
Replace nonsensical `from {} / http` patterns with realistic examples
that show http enriching actual input data.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Document the new `on_backlog` option for `serve_http` and explain the `buffer`, `block`, and `drop` behaviors. Add an example that shows how to apply backpressure until a client connects.
b7f3dcc to
89e315c
Compare
Summary
accept_httpoperator (HTTP server that accepts incoming requests as events)from_httpdocumentation to reflect the new client-only design with$responsepipeline variable (replacingmetadata_fieldandserver=truemode)accept_httpcross-reference to thehttpoperator's See Also sectionRelated PRs
Test plan
accept_http.mdxrenders correctly with all sectionsfrom_http.mdxno longer referencesserver=truemodeaccept_http,from_http, andhttp🤖 Generated with Claude Code