Skip to content

fix: correct DLQ runbook CEL null-check guidance #213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ecv wants to merge 1 commit into from
Closed

fix: correct DLQ runbook CEL null-check guidance #213

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions docs/runbooks/dlq/policy-dlq-errors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,12 +92,15 @@ kubectl edit activitypolicy <policy-name>
# After: has(audit.verb) && audit.verb == 'create'

# 2. Add null checks for nested fields
# Guard the full leaf path, not just the root object: responseObject can be
# present while metadata.name is absent (DELETE, status subresource, error
# responses), which still raises "no such key: name".
# Before: audit.responseObject.metadata.name
# After: has(audit.responseObject) ? audit.responseObject.metadata.name : audit.objectRef.name
# After: has(audit.responseObject.metadata.name) ? audit.responseObject.metadata.name : audit.objectRef.name

# 3. Handle DELETE operations (no responseObject)
# Before: {{ audit.responseObject.spec.type }}
# After: {{ has(audit.responseObject) ? audit.responseObject.spec.type : 'deleted' }}
# After: {{ has(audit.responseObject.spec.type) ? audit.responseObject.spec.type : 'deleted' }}
```

Policy update triggers immediate retry of all failed events.
Expand Down