Skip to content

docs(issues): ISSUE-166, security annotation primitives read back as 0 / false when unset - #496

Merged
dwolfson merged 1 commit into
odpi:mainfrom
dwolfson:docs/issue-166-primitive-defaults
Oct 26, 2026
Merged

dwolfson merged 1 commit into
odpi:mainfrom
dwolfson:docs/issue-166-primitive-defaults

Conversation

@dwolfson

Copy link
Copy Markdown
Member

Records ISSUE-166 in PYEGERIA_ISSUES.md (open Egeria Server issues) and EGERIA_OPEN_ISSUES.md.

Egeria's SecurityFindingAnnotationProperties, VulnerabilityAnnotationProperties and SecurityPostureAnnotationProperties declare cvssScore, exploitAvailable, patchAvailable and the posture counts as Java primitives. An unset value therefore reads back as 0 or false. This was confirmed live on 2026-10-26: a vulnerability created with only a severity came back with cvssScore: 0.0 and exploitAvailable: false.

The entry includes a question for the Egeria team: could these become boxed types with a null default? It also records the pyegeria display workaround in #495.

Docs only.

🤖 Generated with Claude Code

…0 / false when unset

Egeria's SecurityFinding/Vulnerability/SecurityPosture annotation properties
classes declare cvssScore, exploitAvailable, patchAvailable and the posture
counts as Java primitives, so an unset value is indistinguishable from 0 or
false (confirmed live 2026-10-26). Records the question for the Egeria team
(boxed types with a null default) and the pyegeria display workaround in
PR odpi#495. Added to EGERIA_OPEN_ISSUES.md as well.

Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
@dwolfson
dwolfson merged commit 0b6c6dc into odpi:main Oct 26, 2026
5 checks passed
@dwolfson
dwolfson deleted the docs/issue-166-primitive-defaults branch October 30, 2026 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant