Univention Bugzilla – Bug 49924
update_extended_attributes() should be idempotent
Last modified: 2019-07-26 16:05:50 CEST
Calling update_extended_attributes() mutliple times should result in a stable outcome. This is currently not the case, e.g. when removing a extended attribute from LDAP and calling update_extended_attributes() a second time, the extended attribute is still in module.mapping. Also module.extended_attribute_tabnames is only cleared once. Everythink which univention.admin.modules.init() does should be idempotent: * update_extended_options() * update_extended_attributes() * etc.