Skip to content

Chore(AIGW): Review entity and provider schemas#5907

Open
Guaris wants to merge 3 commits into
release/ai-gateway-2.0from
entity-yaml-test
Open

Chore(AIGW): Review entity and provider schemas#5907
Guaris wants to merge 3 commits into
release/ai-gateway-2.0from
entity-yaml-test

Conversation

@Guaris

@Guaris Guaris commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Reviewed all of these, tested schemas were valid, checked i nKonnect

@Guaris Guaris requested a review from a team as a code owner July 10, 2026 20:13
Copilot AI review requested due to automatic review settings July 10, 2026 20:13

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 11 out of 11 changed files in this pull request and generated no comments.

@netlify

netlify Bot commented Jul 10, 2026

Copy link
Copy Markdown

Deploy Preview for kongdeveloper ready!

Name Link
🔨 Latest commit c2868b1
🔍 Latest deploy log https://app.netlify.com/projects/kongdeveloper/deploys/6a523bba09459400088dd49a
😎 Deploy Preview https://deploy-preview-5907--kongdeveloper.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@lena-larionova lena-larionova left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whatever skill or instructions that were used to make this PR need updating.

  • Don't use em dashes (or dashes in general)
  • Don't use positional language like "below" and "above"

Comment thread app/_ai_gateway_entities/ai-agent.md Outdated
The following example creates an `a2a` Agent that proxies traffic to an upstream A2A agent at `https://booking-agent.internal.kongair.com`, with statistics logging enabled and access restricted to the `internal-teams` Consumer Group.

{:.info}
> This example proxies to a placeholder upstream at `https://booking-agent.internal.kongair.com`. Substitute the URL of your own running A2A agent in [`config.url`](#schema-aigateway-agent-config-url). Because this Agent has `type: a2a`, requests must use the A2A JSON-RPC envelope (`jsonrpc: "2.0"`, `id`, `method: "message/send"`, `params.message` with `kind` and `messageId`)—a flat `{"message": {...}}` body without that envelope is rejected by the upstream agent itself (for example, `"Invalid Request: jsonrpc must be 2.0"`), not by {{site.ai_gateway}}.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both this item and the note about "AI Consumer Group to reference in [access.acls]" are prerequisites. They should be grouped together. Maybe this needs to be split into a short "prerequisites" section, and then the rest can be in a section titled "Example"?

Eg

## Set up an Agent

Blurb about setting up agents.

### Prerequisites

* Before creating an AI Agent with access restrictions, create an AI Consumer Group to reference in [`access.acls`](#schema-aigateway-agent-access). 
This example references a group named `internal-teams`. See [Set up an AI Consumer Group](/ai-gateway/entities/ai-consumer-group/#set-up-an-ai-consumer-group) to create it, or substitute the name of your own AI Consumer, AI Consumer Group, or Authenticated Group in `access.acls.allow`.

* Start an A2A agent and take note of its URL.

### Example

The following example creates an `a2a` Agent that proxies traffic to an upstream A2A agent at `https://booking-agent.internal.kongair.com`, with statistics logging enabled and access restricted to the `internal-teams` Consumer Group.

Replace the placeholder upstream URL `https://booking-agent.internal.kongair.com` with the URL of your own running A2A agent in [`config.url`](#schema-aigateway-agent-config-url). Because this Agent has `type: a2a`, requests must use the A2A JSON-RPC envelope (`jsonrpc: "2.0"`, `id`, `method: "message/send"`, `params.message` with `kind` and `messageId`)—a flat `{"message": {...}}` body without that envelope is rejected by the upstream agent itself (for example, `"Invalid Request: jsonrpc must be 2.0"`), not by {{site.ai_gateway}}.

Comment thread app/_ai_gateway_entities/ai-consumer-group.md Outdated
Comment thread app/_ai_gateway_entities/ai-consumer-group.md Outdated
Comment thread app/_ai_gateway_entities/ai-consumer.md Outdated
Comment thread app/_ai_gateway_entities/ai-consumer.md Outdated
Comment thread app/_ai_gateway_entities/ai-model.md Outdated
Comment thread app/_ai_gateway_entities/ai-policy.md Outdated
Comment thread app/_ai_gateway_entities/ai-vault.md Outdated
Co-authored-by: lena-larionova <54370747+lena-larionova@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants