Skip to content

Feat(AIGW): Add AI Prompt Compressor v2 Policy docs for Headroom integration - #7283

Draft
Guaris wants to merge 3 commits into
mainfrom
docs/ai-prompt-compressor-v2-headroom
Draft

Guaris wants to merge 3 commits into
mainfrom
docs/ai-prompt-compressor-v2-headroom

Conversation

@Guaris

@Guaris Guaris commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Documents ai-prompt-compressor-v2 as a new AI Gateway 2.0 Policy (kong-ee#21675), covering both its kong and headroom compression providers. Sourced from the PR's actual schema/handler code rather than the PRD/ticket's field list, since the two diverge (see PR description for details). Adds a cross-link from the existing ai-prompt-compressor Policy page and a scopes.json entry.

Description

Fixes #issue

Preview Links

Checklist

  • Tested how-to docs. If not, note why here.
  • All pages contain metadata.
  • Any new docs link to existing docs.
  • All autogenerated instructions render correctly (API, decK, Konnect, Kong Manager).
  • Style guide (capitalized gateway entities, placeholder URLs) implemented correctly.
  • Every page has a description entry in frontmatter.
  • Add new pages to the product documentation index (if applicable).

@Guaris
Guaris requested a review from a team as a code owner September 17, 2026 20:46
@Guaris Guaris added the do not merge Issues/ PRs whose changes should not be merged at this time label Sep 17, 2026
@netlify

netlify Bot commented Sep 17, 2026

Copy link
Copy Markdown

Deploy Preview for kongdeveloper ready!

Name Link
🔨 Latest commit 759f5a2
🔍 Latest deploy log https://app.netlify.com/projects/kongdeveloper/deploys/6aac56152f5f8e0008cf4a91
😎 Deploy Preview https://deploy-preview-7283--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.

@Guaris
Guaris marked this pull request as draft September 17, 2026 20:47
Documents ai-prompt-compressor-v2 as a new AI Gateway 2.0 Policy
(kong-ee#21675), covering both its kong and headroom compression
providers. Sourced from the PR's actual schema/handler code rather
than the PRD/ticket's field list, since the two diverge (see PR
description for details). Adds a cross-link from the existing
ai-prompt-compressor Policy page and a scopes.json entry.
@Guaris
Guaris force-pushed the docs/ai-prompt-compressor-v2-headroom branch from ad61eeb to 5d552c3 Compare September 17, 2026 20:55
…2 Policy

Jekyll::Policies::Base#name does metadata.fetch('name') with no
default. Policies with a backing app/_kong_plugins/ page inherit
name/title/icon/etc. from it; this Policy has none (deliberately, per
the Konnect-only scope decision), so it must supply them directly in
its own frontmatter, matching the ai-nvidia-nemo-guardrail precedent
(the only other backing-plugin-less AI Gateway policy in the repo).

Fixes the build crash: key not found: "name" (KeyError) in
app/_plugins/generators/policies/base.rb:44.
Fold Headroom support into ai-prompt-compressor as a second backend
(alongside the existing LLMLingua 2 / kong compressor service backend)
instead of a separate ai-prompt-compressor-v2 Policy. The v2 split
mirrored a Gateway-plugin-level naming decision from kong-ee#21675
(which keeps ai-prompt-compressor byte-identical and ships Headroom
under a new plugin name for its own backward-compat reasons), but
that's an implementation-internal detail, not a product decision.
The PRD's own "purely additive" framing, and the real
developer.konghq.com#7123 precedent, both treat this as one Policy
gaining a new backend, not two Policies.

Left a TODO flagging that the exact Headroom config field names/shape
still need re-verification once kong-ee#21675 (or whatever supersedes
it) actually lands, since as of now no code adds Headroom fields to
ai-prompt-compressor's own schema.

Deletes the ai-prompt-compressor-v2 Policy page and its scopes.json
entry.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Issues/ PRs whose changes should not be merged at this time

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant