Bug 49923 - Automatically call modules.update() initiailly when using modules.get()
Automatically call modules.update() initiailly when using modules.get()
Status: NEW
Product: UCS
Classification: Unclassified
Component: UDM (Generic)
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-07-26 15:13 CEST by Florian Best
Modified: 2024-03-07 14:39 CET (History)
0 users

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2019-07-26 15:13:12 CEST
univention.admin.modules.get() should check if univention.admin.modules.update() has been called before and if not, call it - for you.
Otherwise `None` is returned which lead to a lot errors in the past and now does again for UVMM code.

The future goal is, to get rid of the necessarity for scripts to call univention.admin.modules.update().
We start with this simple attempt, so it's not necessary to call update() at import-time of UDM.
Comment 1 Florian Best univentionstaff 2019-07-26 15:53:47 CEST
Not now. There are potential risks for recursion errors.
Comment 2 Florian Best univentionstaff 2024-03-07 14:39:58 CET
Since git:f56259d79f47767d440695703210626f96e8233d Bug #50385 there is the internal function univention.amdin.modules._get() doing this.