Skip to content

feat(event-gateway): Request rule validator policy - #7303

Open
lena-larionova wants to merge 2 commits into
release/event-gateway-1.3from
feat/rule-validator
Open

lena-larionova wants to merge 2 commits into
release/event-gateway-1.3from
feat/rule-validator

Conversation

@lena-larionova

@lena-larionova lena-larionova commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

Description

New event gateway policy in 1.3: request rule validator. This adds the policy ref doc and an example.

Note: can't test this yet, the API isn't updated in Konnect.

Preview Links

/event-gateway/policies/request-rule-validator/

@netlify

netlify Bot commented Sep 19, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for kongdeveloper ready!

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

@jakubdyszkiewicz jakubdyszkiewicz 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.

some nits, but looks good overall

I think we need more examples. This feature exposes quite a lot of things but we only put one example. I'll try to contribute it on followup PRs

* Block changes to broker-level configuration.
* Prevent overly permissive ACL bindings, like granting `ALL` or using a wildcard principal.

Each rule describes the valid state of a request as a [CEL expression](/event-gateway/expressions/). When the expression evaluates to `false`, the rule's configured action runs.

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.

Suggested change
Each rule describes the valid state of a request as a [CEL expression](/event-gateway/expressions/). When the expression evaluates to `false`, the rule's configured action runs.
Each rule describes the valid state of a request as a [gateway expression](/event-gateway/expressions/). When the expression evaluates to `false`, the rule's configured action runs.

remove CEL for now

### Request types and available values

You configure rules per Kafka request type.
Each request type exposes a different set of values to the rule's CEL expression, matching the fields of that request.

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.

Suggested change
Each request type exposes a different set of values to the rule's CEL expression, matching the fields of that request.
Each request type exposes a different set of values to the rule's expression, matching the fields of that request.

Each rule configures one of two actions, which runs when the rule's expression evaluates to `false`:

* `reject`: Fails the request, or the offending item in a batch, with the `POLICY_VIOLATION` error code.
* `passthrough`: Lets the request continue, but records the violation the same way `reject` does.

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.

Suggested change
* `passthrough`: Lets the request continue, but records the violation the same way `reject` does.
* `passthrough`: Lets the request continue, but records the violation the same way `reject` does (metrics and logs on a debug level).

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.

3 participants