Skip to content

Document accept_http and update HTTP operators#212

Open
mavam wants to merge 12 commits intotopic/new-executorfrom
topic/http-with-proxygen
Open

Document accept_http and update HTTP operators#212
mavam wants to merge 12 commits intotopic/new-executorfrom
topic/http-with-proxygen

Conversation

@mavam
Copy link
Copy Markdown
Member

@mavam mavam commented Feb 17, 2026

Summary

  • Add documentation for the new accept_http operator (HTTP server that accepts incoming requests as events)
  • Update from_http documentation to reflect the new client-only design with $response pipeline variable (replacing metadata_field and server=true mode)
  • Add accept_http cross-reference to the http operator's See Also section

Related PRs

Test plan

  • Verify accept_http.mdx renders correctly with all sections
  • Verify from_http.mdx no longer references server=true mode
  • Verify cross-references resolve between accept_http, from_http, and http

🤖 Generated with Claude Code

@github-actions github-actions bot added the reference Reference documentation label Feb 17, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 17, 2026

📦 Preview  ·  View →  ·  🟢 Live

Auto-updates on push

@github-actions github-actions bot added guide How-to guides integration Integration documentation site Site infrastructure labels Feb 18, 2026
@mavam mavam force-pushed the topic/http-with-proxygen branch from 592fd96 to 8b171ef Compare February 18, 2026 16:15
@mavam mavam force-pushed the topic/new-executor branch from 8c59ee1 to 3886444 Compare February 19, 2026 12:21
@mavam mavam marked this pull request as ready for review February 19, 2026 17:05
@mavam mavam force-pushed the topic/new-executor branch from 588262f to 17b8b2b Compare February 25, 2026 21:26
@mavam mavam force-pushed the topic/http-with-proxygen branch from 8b171ef to 15faf9d Compare March 16, 2026 19:34
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 16, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5bec67a7-ddf3-48df-a190-96e801cd6954

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch topic/http-with-proxygen
📝 Coding Plan
  • Generate coding plan for human review comments

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

Tip

You can disable sequence diagrams in the walkthrough.

Disable the reviews.sequence_diagrams setting to disable sequence diagrams in the walkthrough.

mavam and others added 12 commits March 16, 2026 20:46
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.
@mavam mavam force-pushed the topic/http-with-proxygen branch from b7f3dcc to 89e315c Compare March 16, 2026 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

guide How-to guides integration Integration documentation reference Reference documentation site Site infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant