docs: sync ADP changes from cloudv2 (2026-06-04)#56
Merged
Conversation
The A2A discovery card (.well-known/agent-card.json) is now served unauthenticated so callers can learn how to authenticate before holding a token. Agent invocation still requires authentication. Document this exception in the agent card and authentication sections. https://claude.ai/code/session_01GbvxcD3FRkSPVJuPmqz69r
✅ Deploy Preview for redpanda-agentic-data-plane ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
[adp-docs PR critic] Verdict: looks accurate. The documented behavior matches the cloudv2 source, the anchor/xref is correct, and the AsciiDoc builds cleanly. Source accuracy (verified against cloudv2)
Correctness
Minor (optional, no action needed)
No critical or blocking issues found. Generated by Claude Code |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Syncs one user-facing ADP (AI Agents / A2A) change from
cloudv2into the docs.The A2A discovery agent card is now served without authentication. Per the A2A spec, the discovery card (
/.well-known/agent-card.json) must be publicly reachable, because a caller fetches it precisely to learn how to authenticate. Previously the card was routed through the authenticated catch-all, so every fetch returned a 401 and discovery was impossible without already holding a token. The fix mounts the card path on a tenancy-only handler ahead of the authenticated catch-all; every other/a2a/v1/*path still requires a valid token.The existing
a2a-concepts.adocpage stated only that "A2A-compliant agents require authentication" and did not note that the discovery card is the exception. This contradicted the new (and spec-correct) behavior, so the change is documented as a clarification.Changes
modules/connect/pages/a2a-concepts.adoc:[#authentication]anchor and a paragraph describing the discovery-card exception (card is served unauthenticated at/.well-known/agent-card.json; every other request, including invocation, requires a valid access token).Preview
Netlify deploy preview (404s until the preview build finishes):
https://deploy-preview-56--redpanda-agentic-data-plane.netlify.app/agentic-data-plane/connect/a2a-concepts/
Source commits
782f557375—aigw: serve A2A agent card without authentication(Refs AI-1313), author @birdayz. https://github.com/redpanda-data/cloudv2/commit/782f5573753b99605dd19a43b57ed3c85d617cdfReviewers
I've added @birdayz (author of the source cloudv2 commit) as an optional reviewer for a source-accuracy check. This review is a courtesy and is not required to merge.
Changes considered but not documented
Other ADP-related commits in the window were reviewed and intentionally excluded as not user-facing documentation changes:
3542314636—feat(aigw): add provider filter to ListGuardrails: adds an internalproviderfilter to theListGuardrailsAPI to back an unshipped UI list control. No user-facing guardrails API reference exists to update, and the UI is still being built. TODO (human review): revisit if/when the guardrails "filter by provider" control ships and warrants a UI doc note.54e089f1e2—proto(adp): constrain agent_uid to UUIDv4: an internalbuf.validateconstraint on theSpendingEvent/SpendingFilteragent_uidfield (spending/budgets API internals). Not surfaced to users.adp-uicommits (guardrails create/edit/list pages, secret store UX, brand icons, transcripts list pagination, visual-regression baselines): front-end/UI work with no documented behavior, config, API, or CLI change.