Skip to content

axonius: fix orValue on non-optional field access in asset CEL programs#19445

Merged
efd6 merged 1 commit into
elastic:mainfrom
efd6:axonius-daily
Jun 9, 2026
Merged

axonius: fix orValue on non-optional field access in asset CEL programs#19445
efd6 merged 1 commit into
elastic:mainfrom
efd6:axonius-daily

Conversation

@efd6

@efd6 efd6 commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Proposed commit message

axonius: fix orValue on non-optional field access in asset CEL programs

The nine asset data streams accessed specific_data with a direct
field reference and called orValue on the non-optional result. This
worked with cel-go v0.25.0 but cel-go v0.28.0 (google/cel-go#1276,
shipped in beats 8.19.16-SNAPSHOT via elastic/mito v1.23.2) correctly
rejects orValue on non-optional types. Change the access to use
optional field selection (.?) so that orValue receives an optional
value as intended.

The three data streams that already used optional access (adapter,
user, gateway) are unaffected.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

@efd6 efd6 self-assigned this Jun 8, 2026
@efd6 efd6 added bugfix Pull request that fixes a bug issue Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] Integration:axonius Axonius labels Jun 8, 2026
…EL programs

The nine asset data streams accessed specific_data with a direct
field reference and called orValue on the non-optional result. This
worked with cel-go v0.25.0 but cel-go v0.28.0 (google/cel-go#1276,
shipped in beats 8.19.16-SNAPSHOT via elastic/mito v1.23.2) correctly
rejects orValue on non-optional types. Change the access to use
optional field selection (.?) so that orValue receives an optional
value as intended.

The three data streams that already used optional access (adapter,
user, gateway) are unaffected.

Fixes elastic#19414
Fixes elastic#19415
Fixes elastic#19416
Fixes elastic#19417
Fixes elastic#19418
Fixes elastic#19419
Fixes elastic#19420
Fixes elastic#19421
Fixes elastic#19422
Fixes elastic#19423
Fixes elastic#19424
Fixes elastic#19425
Fixes elastic#19426
Fixes elastic#19427
Fixes elastic#19428
Fixes elastic#19429
Fixes elastic#19430
Fixes elastic#19431
@efd6 efd6 force-pushed the axonius-daily branch from 45ca962 to c26baee Compare June 8, 2026 22:44
@github-actions

github-actions Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown

✅ All changelog entries have the correct PR link.

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine

Copy link
Copy Markdown

💚 Build Succeeded

cc @efd6

@efd6 efd6 marked this pull request as ready for review June 8, 2026 23:18
@efd6 efd6 requested a review from a team as a code owner June 8, 2026 23:18
@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@efd6 efd6 changed the title packages/axonius: fix orValue on non-optional field access in asset CEL programs axonius: fix orValue on non-optional field access in asset CEL programs Jun 8, 2026
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown

Package axonius - 0.1.1 containing this change is available at https://epr.elastic.co/package/axonius/0.1.1/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment