Skip to content

feat(event-gateway): CEL support in KEG - #7285

Open
lena-larionova wants to merge 11 commits into
mainfrom
feat/keg-cel-support
Open

lena-larionova wants to merge 11 commits into
mainfrom
feat/keg-cel-support

Conversation

@lena-larionova

@lena-larionova lena-larionova commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Description

Event Gateway is switching to CEL expression syntax, similar to API Gateway. In this case though, the CEL syntax is going to completely replace the existing JS-style syntax in some near future. Therefore, instead of creating a new page and maintaining a legacy version one, I added the reference to the existing doc and moved the JS info into its own section.

  • I did remove the JS examples section, as we don't really need/want to guide them there anymore
  • I chose to leave the other pieces for now, temporarily, for any customers that are still on the old styntax. We should remove it when the syntax is deprecated and customers are all migrated.
  • Note: This is a CP feature, so it's not gated by a release version. No new_in tags needed.

As a side benefit, also fixes #5309.

Preview Links

https://deploy-preview-7285--kongdeveloper.netlify.app/event-gateway/expressions/

@netlify

netlify Bot commented Sep 17, 2026

Copy link
Copy Markdown

Deploy Preview for kongdeveloper ready!

Name Link
🔨 Latest commit f04d794
🔍 Latest deploy log https://app.netlify.com/projects/kongdeveloper/deploys/6aadbfee812cd800087b8f74
😎 Deploy Preview https://deploy-preview-7285--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 added this to the Event Gateway 1.3 milestone Sep 18, 2026

@mlavacca mlavacca left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good to me! I've added a nit suggestion. Feel free to accept it or merge as is.

Comment thread app/event-gateway/entities/policy.md Outdated
lena-larionova and others added 9 commits September 18, 2026 16:59
The Konnect API host was hardcoded to konghq.com, so a how-to could
not be rendered or tested against the internal konghq.tech
environment. EnvironmentVariablesGenerator now reads KONNECT_DOMAIN
(default konghq.com) into site.config, and the drop builds its host
from that value instead of the literal.
The runner only forwarded TESTS_-prefixed env vars, so KONNECT_DOMAIN
and KONGCTL_DEFAULT_KONNECT_ENVIRONMENT never reached the container.
runtimeEnvironment now passes both through unprefixed, and derives
KONNECT_CONTROL_PLANE_URL (plus its DECK_ twin) and
KONGCTL_DEFAULT_KONNECT_ENVIRONMENT=tech from KONNECT_DOMAIN.
TESTS_KONNECT_CONTROL_PLANE_URL in .env.test and the KONNECT_DOMAIN/
KONGCTL_DEFAULT_KONNECT_ENVIRONMENT env vars on the on-prem AI Gateway
runtime pinned every run to konghq.tech. The runner now derives these
from KONNECT_DOMAIN, so a run with no domain set targets konghq.com.
The Event Gateway cleanup commands called the Konnect API directly
against a hardcoded us.api.konghq.com host, so a .tech run's cleanup
still hit production. Both calls now read KONNECT_DOMAIN.
A maintainer had no way to build the site or run the Event Gateway
tests against konghq.tech from CI. run-site takes a konnect-domain
input, and the workflow adds a konnect_domain workflow_dispatch input
that flows to run-site, the test runner, and selects the matching
Konnect token secret.
Mirrors the Event Gateway workflow's konnect_domain input: it flows
to run-site, to the test runner, and selects KONNECT_TOKEN_TECH over
KONNECT_TOKEN when set, so a maintainer can dispatch a .tech run.
Co-authored-by: Mattia Lavacca <lavacca.mattia@gmail.com>
@lena-larionova lena-larionova self-assigned this Sep 18, 2026
@lena-larionova lena-larionova removed this from the Event Gateway 1.3 milestone Sep 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document Event Gateway matching context

4 participants