[dwolfson]

Summary

Egeria 6.3 now uses boxed types for the numbers and flags in its property beans (odpi/egeria#9389, merged as 12b1aaae). An unset value is left out of the response, and a merge update keeps a value it doesn't mention. This fixes ISSUE-166. This PR adapts pyegeria to that change and also fixes a bearer-token bug reported by a user.

Boxed properties

• Dr.Egeria upsert: when a Create finds the element already exists and becomes an Update, it no longer sends the spec defaults the parser filled in for the Create (e.g. isNullable: true, position: 0). On 6.3 those would overwrite stored values. Only Merge Update keeps its default. See AsyncBaseCommandProcessor._drop_create_defaults.
• No more forced 0s: GovernanceControlProperties.domain_identifier, EmbeddedConnectionProperties.position, Person/Team Role headCount and Solution Role domainIdentifier are now left unset when not given.
• ISSUE-166 workarounds removed:
  • DataDiscovery._security_row shows a returned 0.0 / false as a real answer.
  • SecurityFindingProcessor no longer copies current values into a merge update.
  • The report spec descriptions, the Dr.Egeria manual and the update_usage_activity docstrings are updated to match.
• ISSUE-166 is marked fixed in PYEGERIA_ISSUES.md / EGERIA_OPEN_ISSUES.md.

Bearer token

create_egeria_bearer_token didn't check the HTTP status. With bad credentials it returned Egeria's 401 error text as the token and put it in the Authorization headers. On a connection error it returned "FAILED". Both base clients now share _post_for_bearer_token, which raises instead and leaves the headers unchanged:

Case	Raises
401 / 403	PyegeriaUnauthorizedException
other non-200	PyegeriaClientException
connection error / timeout	PyegeriaConnectionException / PyegeriaTimeoutException
empty body, or an Egeria JSON error body	PyegeriaInvalidParameterException

Note for callers

Elements written by servers older than 6.3 still hold a stored 0 / false for values nobody set; #9389 doesn't migrate them. Code that compared the token result to "FAILED" should catch the exception instead.

Testing

• Micro-tests: 1538 collected, 0 failed. New tests: test_create_bearer_token_errors.py (7 cases) and test_upsert_drops_create_defaults.py.
• Live, 2026-10-27, on egeria-platform c2ca054c (6.3-SNAPSHOT) as erinoverview on qs-view-server:
  • A wrong password raises PyegeriaUnauthorizedException.
  • A VulnerabilityAnnotation created with only a severity came back without cvssScore / exploitAvailable / patchAvailable.
  • After those were set to 8.6 / true / false, a description-only merge update kept all three, and the explicit false came back as false.
  • The throwaway was deleted, and a read-back by GUID returned 404.
• Not live-tested: the Dr.Egeria upsert-default change (unit-tested only).

🤖 Generated with Claude Code