Univention Bugzilla – Bug 54708
Kelvin plugin and derivates do not properly handle none values
Last modified: 2022-05-11 12:31:55 CEST
The ID Connector lets plugins decide how to handle None values in the changed data that is to be synced. The Kelvin plugin handles none values like this: def _handle_none_value(self, key_here: str) -> Any: """`none` can be invalid, for example if a list is expected.""" if key_here in ("birthday", "userexpiry"): return None raise SkipAttribute() Meaning: birthday and userexpiry are synced with None as values, all others are skipped and not transmitted to target API. The Kelvin plugin needs proper support for nullable school values as well as mapped udm properties! We should just transmit all None values of udm properties that are incoming. For that we could check if a value is a school value (KELVIN_API_SCHOOL_ATTRIBUTES) or not.
Added additional information and set Waiting Support together with Dirk Schnick.