Bug 58272 - Possible UDM syntax extension import conflicts
Summary: Possible UDM syntax extension import conflicts
Status: RESOLVED MOVED
Alias: None
Product: UCS
Classification: Unclassified
Component: UDM - Extended Attributes
Version: UCS 5.0
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UMC maintainers
QA Contact: UMC maintainers
URL: https://git.knut.univention.de/univen...
Keywords:
Depends on: 57630
Blocks:
  Show dependency tree / graph
 
Reported: 2025-05-14 17:15 CEST by Arvid Requate
Modified: 2025-07-28 20:53 CEST (History)
5 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.137
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
Max CVSS v3 score:
best: Patch_Available+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2025-05-14 17:15:15 CEST 
The same issue as reported for UDM hooks and fixed via Bug #57630 also applies to UDM syntax extensions.

The sandboxing import that is now used for UDM hooks may cause regressions for UDM syntax extensions in case authors didn't explicitly import dependencies but relied on implicit prior imports in the global namespace. We need to find a middle ground here or use some kind of UCS release to communicate the possible breaking change and give customers proper time for testing and possibly required adjustments.