feat(event-gateway): CEL support in KEG - #7285
Open
lena-larionova wants to merge 11 commits into
Open
lena-larionova wants to merge 11 commits into
lena-larionova wants to merge 11 commits into
Conversation
✅ Deploy Preview for kongdeveloper ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
mlavacca
approved these changes
Sep 18, 2026
mlavacca
left a comment
Member
There was a problem hiding this comment.
Looks good to me! I've added a nit suggestion. Feel free to accept it or merge as is.
lmilan
approved these changes
Sep 18, 2026
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.
fabianrbz
force-pushed
the
feat/keg-cel-support
branch
from
September 18, 2026 14:59
a6c7552 to
c9bbcb9
Compare
Co-authored-by: Mattia Lavacca <lavacca.mattia@gmail.com>
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.
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.
As a side benefit, also fixes #5309.
Preview Links
https://deploy-preview-7285--kongdeveloper.netlify.app/event-gateway/expressions/